Form-based user-configurable processing plant management system and method

ABSTRACT

A computer-implemented system and method for defining the processes in a processing plant are disclosed. In one embodiment, the system uses input forms to allow a user to define the processes, chemicals, process streams, and sampling points in the plant in a way that requires no programming code to be written by the person defining the plant. In one embodiment, the electronic form-based user-configurable system can be used to configure and manage multiple plants belonging to one organization. The plant definition can be used to log information about the plant. The logged information can be used to generate reports or charts. Logging, reporting, and charting can be managed using input forms and without the user needing to write any computer code.

No related U.S. or foreign application data.

BACKGROUND OF THE DISCLOSURE

Current practices relating to data management of plant operational dataare typically based (1) on paper-based log data storage, where operatorswho operate the plant collect information from the plant and store theinformation in a paper notebook or (2) on Supervisory Control and DataAcquisition (SCADA) systems, which are pre set two-way controls commonlyused to operate the plant at critical points in the process and requiresomeone with computer programming skills to configure and set up.

Paper-based information storage has been practiced because of regulatoryrequirements. Governmental agencies typically require plant managers toreport regulated parameters in a paper format. This results in asignificant drawback from an operational point of view, the inabilityfor plant managers to readily access the data and perform data trendinganalysis. As a result of this situation, plant managers are unable touse these data to perform optimization changes. In many instances, suchpaper-based information is simply not available on time, to be includedin any decision making process, because most chemical plants are locatedin isolated locations significantly removed from the location ofadministrative and executive staff. In addition, most chemical plantsemploy external entities such as consulting engineering firms,laboratories and subject matter experts to assist in the optimaloperation of chemical based plants. This process typically involvesproviding plant operational data to the requisite parties so thatcorrect analysis can be conducted. Because information is stored onpaper, significant processing time is incurred in understanding andinterpreting operational notes, thus increasing operational costs.

Plants also suffer from human attrition. For example, when operatingpersonnel leave the plant, operational intelligence and knowledge tiedto the employee are no longer available to the organization. This, whencoupled with paper-based information storage makes the problem ofcorrectly interpreting plant operational data logged by an employee whohas left the organization, more acute.

Some plants have adopted automation as the solution, where a portion orthe whole plant is automated, and information is logged using datalogging devices placed at different locations in the plant flow scheme.This approach is often referred to as SCADA. For the most part, thebrains of a SCADA system are performed by the Remote Terminal Units(RTU), which consists of a programmable logic converter. The RTU areusually set to specific requirements, and monitor specific processes ina given treatment train. In addition to the RTU, a SCADA system requiresa Human Machine Interface (HMI). The HMI of a SCADA system processesdata and presents it be viewed and monitored by a human operator. Thisinterface usually includes controls where the individual can interfacewith the SCADA system.

The introduction of SCADA and automation in facilities has significantlyimproved operational reliability and operator response time, On theother hand, SCADA systems remain an expensive option for small to mediumsize plants, which do not have the operational budget to supportautomation devices and programs. SCADA systems are not flexible—devicecompatibility, system upgrades or plant modifications are key concerns.In addition, it is critical to understand that SCADA systems cannot beused as a compliance-reporting tool because SCADA systems focus onoperating parameters. SCADA systems have also been identified as apotential vulnerability and opening SCADA to the web has become a riskand security concern.

With the advent of the web and web-like communication options, theability of closing the gap between automated and paper-based operationaldata storage with a computer implemented approach is now possible. Thereis a need for a system and method that enables users to store andretrieve data without loss of time and resources. Such a system shouldmeet the following criteria:

-   -   capable of meeting all operational and regulatory reporting        requirements;    -   capable of being configured to describe any processing plant        without requiring the use of any programming skill;    -   capable of combining automated and non-automated data;    -   provide pre-defined reports;    -   capable of setting alerts;    -   capable of providing different levels of access to different        users who serve in different roles;    -   and be highly secure while operating over a widely-available        information medium such as the internet.

SUMMARY OF THE INVENTION

The present invention uses electronic forms in a client-serverenvironment to allow a user to define a processing plant. Thisdefinition of the plant can include processes, chemicals, processstreams, and sampling points in the plant. The plant definition can beused to log information about the plant. The logged information can beused to generate reports or charts. Logging, reporting, and charting canbe managed using electronic input forms on computer screens without theuser needing to write any computer code. In one embodiment, multipleprocessing plants can be grouped into one organization and the data frommultiple organizations can be managed in one computer system. In oneembodiment, access to different parts of the system can be controlledthrough modules that manage users and functions.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appendedfigures in which:

FIG. 1 is a schematic identifying the key components of a web serverapplication;

FIG. 2 is a schematic identifying user types of the web serverapplication;

FIG. 3 illustrates key access levels used to define the User PermissionComponent;

FIG. 4 is a user access summary table of the different user accesslevels;

FIG. 5 illustrates the functionalities of the User Permission Component;

FIG. 6 illustrates the functionalities of the Administer Component;

FIG. 7 illustrates the functionalities of the Define Component;

FIG. 8 illustrates key Modules under the Define Component;

FIG. 9 illustrates the functionalities of the Data Logging Component;

FIG. 10 illustrates the functionalities of the Data Reporting Component;

FIG. 11 illustrates the functionalities of the User Homepage Component;

FIG. 12 is a display of an Organization Adding/Editing Module;

FIG. 13 is a display of an Organization Listing Module;

FIG. 14 is a display of a User Adding Module;

FIG. 15 is a display of a User Access Permission Adding Module;

FIG. 16 is a display of a User Listing Module;

FIG. 17 is a display of a User Editing Module;

FIG. 18 is a display of a Plant Adding Module;

FIG. 19 is a display of a Plant Listing Module;

FIG. 20 is a display of a Plant Editing Module;

FIG. 21 is a display of a Global Parameter Adding Module;

FIG. 22 is a display of a Global Parameter Listing Module;

FIG. 23 is a display of a Global Parameter Editing Module;

FIG. 24 is a display of a Global Task Adding Module;

FIG. 25 is a display of a Global Task Listing Module;

FIG. 26 is a display of a global Task Editing Module;

FIG. 27 is a display of an Organization Files and Links Management AddModule;

FIG. 28 shows an Organization Files and Links Management Add/ListingModule;

FIG. 29 is a display of an Organization Files and Links Management EditModule;

FIG. 30 is a display of a Plant Selection Module;

FIG. 31 is a display of a Parameter Adding Module;

FIG. 32 is a display of a Parameter Listing Module;

FIG. 33 is a display of a Parameter Editing Module;

FIG. 34 is a display of a Chemical Adding Module;

FIG. 35 is a display of a Chemical Listing Module;

FIG. 36 is a display of a Chemical Editing Module;

FIG. 37 is a display of a Process Node Adding Module;

FIG. 38 is a display of a Process Node Listing Module;

FIG. 39 is a display of a Process Node Editing Module;

FIG. 40 is a display of a Process Stream Connection Adding Module;

FIG. 41 is a display of a Process Stream Connection Listing Module;

FIG. 42 is a display of a Process Stream Connection Editing Module;

FIG. 43 is a display of a Sampling Point Adding Module;

FIG. 44 is a display of a Sampling Point Listing Module;

FIG. 45 is a display of a Sampling Point Editing Module;

FIG. 46 is a display of an Issue Type Adding Module;

FIG. 47 is a display of an Issue Type Listing Module;

FIG. 48 is a display of an Issue Type Editing Module;

FIG. 49 is a display of a Notification Adding Module;

FIG. 50 is a display of a Notification Listing Module;

FIG. 51 is a display of a Notification Editing Module;

FIG. 52 is a display of a Task Adding Module;

FIG. 53 is a display of a Task Listing Module;

FIG. 54 is a display of a Task Editing Module;

FIG. 55 is a display of an Action Adding Module;

FIG. 56 is a display of a Action Listing Module;

FIG. 57 is a display of an Action Editing Module;

FIG. 58 is a display of a Plant Log Selection Module;

FIG. 59 is a display of a Plant Log Adding Module;

FIG. 60 is a display of a Plant Log Search Module;

FIG. 61 is a display of a Plant Log Editing Module;

FIG. 62 is a display of a Process Log Adding Module;

FIG. 63 is a display of a Process Log Search/Listing Module;

FIG. 64 is a display of a Process Log Editing Module;

FIG. 65 is a display of a Process Stream Log Adding Module;

FIG. 66 is a display of a Process Stream Log Search/Listing Module;

FIG. 67 is a display of a Process Stream Log Editing Module;

FIG. 68 is a display of a Sampling Point Log Adding Module;

FIG. 69 is a display of a Sampling Point Log Search/Listing Module;

FIG. 70 is a display of a Sampling Point Log Editing Module;

FIG. 71 is a display of an Issue Log Adding Module;

FIG. 72 is a display of an Issue Log Search/Listing Module;

FIG. 73 is a display of an Issue Log Editing Module;

FIG. 74 is a display of a Plant Selection Module;

FIG. 75 is a display of a Report Creating Module;

FIG. 76 is a display of a Report Listing and Archiving Module;

FIG. 77 is a display of a Report Generating Module;

FIG. 78 is a display of a Report Publishing Module;

FIG. 79 is a display of a Chart Creating Module;

FIG. 80 is a display of a Chart Listing and Archiving Module;

FIG. 81 is a display of a Chart Generating Module;

FIG. 82 is a display of a Chart Publishing Module;

FIG. 83 is a display of a Model Adding Module;

FIG. 84 is a display of a Model Listing Module;

FIG. 85 is a display of a Model Running Module;

FIG. 86 is a display of a Model Publishing Module;

FIG. 87 is a display of a Form Adding Module;

FIG. 88 is a display of a Form Adding Module;

FIG. 89 is a display of a Form Funning Module;

FIG. 90 is a display of a Form Publishing Module;

FIG. 91 is a display of a Global Report Creating Module;

FIG. 92 is a display of a Global Report Listing and Archiving Module;

FIG. 93 is a display of a Global Report Generating Module;

FIG. 94 is a display of a Global Report Publishing Module;

FIG. 95 is a display of a Chart Creating Module;

FIG. 96 is a display of a Chart Listing and Archiving Module;

FIG. 97 is a display of a Chart Generating Module;

FIG. 98 is a display of a Chart Publishing Module;

FIG. 99 is a display of a Plant Selection Module;

FIG. 100 is a display of a User Specific Notification Listing andSelection Module;

FIG. 101 is a display of a User Specific Plant Action Listing Module;

FIG. 102 is a display of an Action Specific Description Module;

FIG. 103 is a display of a Task Description Module;

FIG. 104 is a display of a User Specific Home Page Dashboard Set UpModule;

FIG. 105 is a display of a User Specific Home Page Dashboard DataSelection Module;

FIG. 106 is a display of a User Specific Home Page Dashboard ChartSelection Module;

FIG. 107 shows a User Specific Home Page Dashboard Pre-Set SelectionModule;

FIG. 108 is a display of a User Profile Viewing and Editing Module;

FIG. 109 is a display of a User Profile Site Access Viewing Module;

FIG. 110 is a display of a Bulletin Board Posting Module;

FIG. 111 is a display of a Bulletin Board Response Module; and

FIG. 112 is a display of a File Downloads and Link Access Module

In the appended figures, similar components and/or features may have thesame reference label. For items with the same reference label, thedescription is applicable to any one of the similar components.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

1—Overview

In the following description, specific details are set forth in order toprovide a clear and thorough understanding of the invention. Theexamples and figures displayed hereafter aim to illustrate the differentfunctionalities associated with the invention, and demonstrate theextent by which the invention can be implemented.

The purpose for the present invention is to enable Plant Managers andother Professionals in equivalent or related positions to effectivelymanage key operational or process data, which would include but wouldnot be limited to numeric data, alpha-numeric data, documents, pictures,video or any other information source or type that would enable anorganization to better manage their facility or facilities. The presentinvention can be used on any plant independently of its location andsize. The present invention can be used for multiple plants under sameorganizations. Among the most obvious benefits this innovation brings toadopting organizations are compliance linkage, efficiency, reliability,savings, and communication; other benefits can be identified throughmore specific applications.

While the core invention provides the user with a great deal of freedomin configuring, managing and organizing its data, the system disclosedhere is also amicable to adding and incorporating an arrangement ofmodules and functionalities which are not viewed as core to theinnovation but can be viewed as business critical. Such modules orfunctions include but are not limited to notification, scheduling, usercontrol access, communication and workflow. The following paragraphswill include some of these modules and functions, as well as components,in addition to the core modules and elements designed in the systemdisclosed here. Finally, the innovation can be structured in anyspecific manner; hence the examples provided hereafter are just anillustration of how the different modules can be organized. The userconfigurability concept core to the invention can be achieved byshifting modules around or even splitting modules while still providingthe same core functionalities. Additionally, the sample screenshotspresented are system-generated forms that can be designed toorganizational user preferences. The critical point is to assure thelinks among the modules are consistent with the goals set forth by theinvention.

The system disclosed here, is based on a thorough understanding of theoperational requirements plant managers face on a daily basis, combinedwith basic chemical engineering principles and computer science. Theinnovation encompasses these three fields through the utilization of aseries of modules and elements; an integrated architecture allows datato flow freely between the modules and elements. For clarity thesemodules and elements were grouped in functional areas or functions whichin turn were grouped under six Components: (a) the User and OrganizationPermission Component, (b) the Administer Component, (c) the DefineComponent, (d) the Data Logging Component, (e) the Data ReportingComponent and (f) the User Homepage Component. The key featuresassociated with the system disclosed here are (a) the point and clickfeatures common across all components that enable the Authorized User toset up the system without the assistance of a programmer, and (b) theability for the Authorized User to perform all necessary functions andactions from one site, including but not limited to data storage, datamanagement, data reporting, workflow management, and alerts ornotifications. Another key feature included in the document is the useof a role-based access control feature associated with the User andOrganization Permission Component. Even though this feature isn't coreto the invention, this feature is critical from an implementation pointof view and in defining the organization full control when adopting thesystem disclosed here described here after.

FIG. 1 illustrates how information flows (102, 104, and 106) to and fromthe user (101) through the internet or intranet (103). As part of thesystem disclosed here, the user (101) accesses the system disclosed herethrough a terminal, which is connected to the internet or a specifiedintranet. The initial command or message (102) flows through theinternet or intranet (103) to the web server application (105). FIG. 1also identifies the key components of the system disclosed here, whichis comprised for clarity purposes, of six interrelated components: Userand Organization Permission Component (107), Administer Component (108),Define Component (116) Data Logging Component (126), Data ReportingComponent (132), User Home Page Component (139), a database (114) and abackup system (115). FIG. 1 only presents the first two levels (i.e.Component and function), while FIGS. 3 through 11 provide additionalinformation on the different Components including the User andOrganization Permission Component and the process by which the formdriven user configurable computer implemented solution enables the userto manage its data. Finally, FIGS. 12 through 112 are sample screendisplays of the specific modules forming the system disclosed here inaddition to those modules that are not core to the invention but arecritical when implementing the system disclosed here. In one embodiment,the system is implemented using a client-server architecture in whichforms are displayed on a client computer and data is stored on a server.Forms can be displayed on a client computer in a variety of ways capableof being understood by any one schooled in the art including textterminals, terminal servers (also known as remote desktop servers), orthrough a web browser. In one embodiment, the client and the servercommunicate by using an internet protocol, also known as TCP/IP or theInternet Protocol Suite.

As mentioned above, the following example requires users to access thesystem disclosed here through the User and Organization PermissionComponent (107). In this component the user's access to the specifiedorganization account must be authorized and authenticated.Authentication is defined as the process of verifying the user's logincredentials (i.e. login and password), before allowing access to theapplication. Authorization is defined as verifying user credentials, andallowing access to only those areas of the application that user isapproved for and preventing access to areas that are not approved. FIGS.3 through 5 provide additional information on the functionalitiesassociated with the User and Organization Permission Component.

Once the user access has been authenticated and authorized by the Userand Organization Permission Component (107), the user is able to accessthe five other Components (1) the Administer Component (108), (2) theDefine Component (116), (3) the Data Logging Component (126), (4) theData Reporting Component (132), and (4) User Home Page Component (139).Within each Component lies a series of functions. FIG. 1 lists the keyfunctions associated with each Component. Located in the AdministerComponent (108) are the Plant Manager Function (109), Global ParameterManager Function (110), the Organization Links and Files ManagerFunction (111), and the Global Task Manager Function (112). Thefunctions located in the Define Component (116) are Parameter ManagerFunction (117), Chemical Manager Function (118), Process ManagerFunction (119), Process Stream Manager Function (120), Sampling PointManager Function (121), Issue Type Manager Function (122), NotificationsManager Function (123), Task Manager Function (124), and Action ManagerFunction (125). The Data Logging Component (126) is formed of the PlantLog Manager Function (127), Process Log Manager Function (128), PlantIssue Type Log Manager Function (129), Process Stream Log ManagerFunction (130), and Sampling Point Log Manager Function (131). In theData Reporting Component (132) are the Plant Report Manager Function(133), Plant Chart Manager Function (134), Plant-specific Model ManagerFunction (135), Plant-specific Form Manager Function (136), GlobalReport Manager Function (137), and Global Chart Manager Function (138).The functions located in the User Homepage Component (139) are GeneralInformation Manager Function (140), Personal Profile Manager Function(141), Workflow Manager Function (142) and the Dashboard ManagerFunction (143). Within each function, an additional hierarchy of modulesis presented. FIGS. 6, 7, 9, 10, and 11 list the modules associated witheach function. The add and edit modules notated in these figures formthe definition modules, which are presented as two separate modules todemonstrate the specific functionalities. The definition modulesinterface with all listing modules. The modules can be arranged in avariety of ways when implementing the system disclosed here. For examplethe editing modules and the adding modules can be designed as onedefinition module. In conjunction with the different modules arefacilitating elements, which will enable the data to be displayed orwill enable the data to move among the different modules, the data base(114) and the backup system (115). The display element enables data tobe presented to the user in a systematic form, thus displays of computergenerated tables and/or checkboxes, charts, reports, and maps arerecurring throughout the system. The data movement element transfers theuser-provided contents of input fields to a computer memory in responseto a signal from a submit or save button and does not requireuser-supplied computer code to transfer.

The system disclosed here described herein that is illustrated in FIG. 1is well-suited for storing and managing operational information from awide range of chemical, process and treatment plants (withoutlimitation), but it is also particularly well-suited for internet-basedapplication and cloud computing type applications. The invention may beimplemented in computer hardware, in computer software, or a combinationof computer hardware and computer software and is not limited to aparticular hardware or software implementation.

In FIG. 1, this user of the system disclosed here was identified as oneentity (101). The users within a specified organization involved in theoperation and management of the system disclosed here as well as anyindividual plant or facility usually encompasses a wide range of users.FIG. 2 identifies key users of the system disclosed here. Among theseusers are system managers (213), organization users (202, 203, and 206)and external users (204, 205, 207, 209, 210, and 211). An example of anorganization user is the facility or plant manager (202) which may haveaccess to a wide range of options including but not limited to changingspecific settings, importing and modifying data, and exporting data.External users, such as consultants (210), are users for whichorganization users grant access to the site or service for a specifictask, hence providing the External user with limited access to thesystem such as read-only rights, due to confidentiality and securitypurposes. Additional information regarding the User and OrganizationPermission Component is provided in FIGS. 3, 4 and 5.

The web server application (212) interfaces with the web (201) and isaccessible to multiple users concurrently. While system upgrades areperformed through the system manager (213), data backups are performedwithin the system. Thus the data is further protected despite theavailable access by multiple user types. The database stores historicaldata as well as current information, which provide the system disclosedhere with audit and tracking capability, necessary in the case ofregulatory applications.

To access the system disclosed here, users may use any of the commonlyavailable means of communication which interfaces with the internetincluding but not limited to laptop computers, desktops, other servers,handheld communication devices, PDAs, any online monitoring deviceincluding SCADA systems. FIG. 3 is an example of an organizational chartidentifying the distinctive user types and how the hierarchicalinteraction is designed. The system disclosed here involves four typesof users: a System Manager User (310), two types of internal ororganizational users, Organization Manager Users (301) and OrganizationOperational Users (304) and lastly a wide variety of External Users(309).

Under the System Manager User category (310) is the System Administrator(311). The System Administrator is responsible for the overallmanagement of the system disclosed here. This would include data backup,creating new Organization Accounts, and providing technical services toall other users. The System Manager User is also the only user categorywhich has access to the computer code which constitutes the systemdisclosed here. Hence this is the only user which has the ability toimplement system wide upgrades. In the example presented here, theSystem Manager User is likely to be a third party provider unrelated tothe organizational account users; however this will not always be thecase.

In FIG. 3, the System Administrator (311) created two organizationalaccounts, Organization 1 (312) and Organization 2 (313). These twoOrganizations are distinct in nature and none of the users underOrganization 1 have access to the portion of the system disclosed hereassigned and developed by Organization 2 and vice versa. Under thesystem disclosed here, data does not cross over among organizationalaccounts.

The next six levels of users involve users that are affiliated to aspecific organization as internal or external users. The first categoryof users is the Organization Manager Users (301). Under this categoryare two levels: the Super Administrator (302) and Administrator (303).Generically, the role of an Administrator is to provide oversight andcontrol on all technical and organizational functionalities associatedwith the operation of the system disclosed here. Hence, theAdministrator has rights to create and modify facilities, overridesettings, produce and modify reports, provide users with login andaccess authentication and authorization, and assist users with anyfunctions associated with the system disclosed here. The role of SuperAdministrator (302) is to assign these managerial capabilities to theAdministrator(s) as corporate guidelines dictate. Thus, the SuperAdministrator has overall authority of the operation and execution ofthe system disclosed here.

The second category of internal or organizational users is theOrganization Operational User (302) which has four levels of hierarchy(a) the Area Manager (305), (b) the Plant Manger (306), theSuperintendent (307) and the Operator (308). Each level corresponds to aspecific user-type function of his or her responsibility. FIG. 4 furtherillustrates the different access levels associated with the differentuser types. Under the system disclosed here, each user type has aspecific role and the system disclosed here will assist the user type toperform its duties.

Under FIG. 3, the Area Manager (305) may have oversight over one or morefacilities. Under the supervision of the Area Manager, the Plant Manager(306) is responsible for defining the process and process streams in thesystem disclosed here that is applicable for each facility. The PlantManager is also responsible for defining the parameters, the actions,the related tasks and all other components listed in the DefineComponent. Once the system disclosed here for each facility is set up,the Plant Manager may assign responsibilities to both the Superintendent(307) and the Operator (308). The Superintendent (307) supervises theOperator (308) and can create as many user operator accounts asemployees under his or her direct supervision.

User access can be granted to External Users (308) by the Plant Manager(306), the Area Manager (305) or any Administrator (302, 303). In thecase where the Plant Manager (305) grants access, the external user willonly have access to specific components and modules as they relate tothe task at hand for the specific facility for which the Plant Managerhas oversight. In the case where a third party provides a service acrossseveral facilities, the Area Manager will grant access to all thefacilities simultaneously. Another possibility could be to have eachPlant Manager grant access to the relevant components or modules for thespecific contractor. For example, an analytical lab may have data inputrights to multiple facilities with no data search rights. In anotherexample, an operational consultant may be responsible for generatingreports across all three facilities. In that case, the operationalconsultant would have read-only rights to the system disclosed here forall three facilities. In a slightly different configuration, a CorporateManager may have access to specific reports that would enable thecorporate manager to perform his or her function. More specificinformation on user access rights are presented in FIG. 4.

FIG. 4 is a summary table for each user type identified in FIG. 3 andtheir respective access rights to the different components of the systemdisclosed here. While FIG. 3 outlined the hierarchy of potential usertypes, FIG. 4 displays the capability for each user type to accessdifferent parts of the system disclosed here.

Under FIG. 4, all user types are listed on the top row of the table(416) and all the components are listed in the first column (409). Thetable illustrates the different access levels to the form-driven userconfigurable computer implemented solution for each user category usingthe following terminology or symbols: (a) no restrictions (indicated bya checkmark), (b) view only, (c) no access (marked by a dash) and (d)Variable, which only applies to external users.

The System Administrator (401) is the only user that has complete accessto the system disclosed here and is able to create, edit and deleteorganizational accounts, which includes identifying the SuperAdministrator for each organization. The System Administrator is alsoresponsible for system maintenance and guarantying access to the site toall authorized and authenticated users.

The Super Administrator (402) has complete access to the components,functions and modules of the system disclosed here dedicated to itsspecific organization. The Super Administrator has more permissions thanany other user for its organizational account and may have access tocertain segments of the original code in the case of special needs orapplications, including but not limited to the modeling, reporting ordata logging. Administrators (403) have comparable access to the webserver application as the Super Administrator (402) except that theAdministrator cannot delete nor edit the Super Administrator Account.

The next level down involves all Organization Operational Users, theArea Manager (404), Plant Manager (405), Superintendent (406) and theOperator (407). Under the current configuration of the web serverapplication, the User and Organization Permission Component (410) isonly accessible to the Area Manger (404) and the Plant Manager (405).The Area Manager (404) is authorized to create accounts for any userthat needs to access the web server application components, functionsand modules dedicated to the facilities under its responsibility,including Plant Mangers (405) or External Users (408). The Plant Manger(405) is authorized to create accounts for any user that requires accessto the web server application components, functions and modulesdedicated to the facility or plant under its responsibility.

Another distinction between the Area Manger (404) and the Plant Manager(405) is the inability for the Plant Manger (405) to create or editplant account information in the Administer Component, since the PlantManger (406) has view-only access, while the Area Manger (404) hascomplete access to the Administer component.

The next levels of Organization Operational Users include theSuperintendent (406) and the Operator (407). Neither of them have theability to access the User and Organization Permission Component (410)nor do they have access to the Add or Edit Modules under the DefineComponent (412). The main differences between the two user levelsinvolve their ability to access the Administer Component (411) as wellas the Data Reporting Component (414). Superintendents (406) haveview-only access to the Administer Component (411), while the Operator(407) does not have access to the Component. The second significantdistinction relates to the Data Reporting Component (414);Superintendents (406) will have complete access to the Data ReportingComponent (414), while the Operator (407) will have partial access withthe ability to view the reports or graphs but not to modify or add anynew reports or graphs.

The last user type is the External Users (408). External Users (408)would be granted access depending on their association to theorganization's facility and their responsibility. The term “Variable”denotes the notion that access can be granted or removed at any giventime by the authorized user. For instance, an External User could haveaccess to the Define Component (412) for a workflow management project,the Data Logging Component (413) if the user was associated with anexternal lab or the Data Reporting Component (414) for a processoptimization case. In any case the Authorized User providing access tothe external user can limit the access to the component depending on theproject or the needs. Due to confidentiality and security purposes, theExternal User may have access only to data pertinent to his or herobjective. The External User (408) will be given complete access to UserHomepage Component (415).

FIG. 5 illustrates how information flows within the boundaries of theUser and Organization Permission Component to the other components ofthe system disclosed here and back to the user. In FIG. 5, the user(501), of the specified organization, accesses the system disclosed hereor web server application (505) through the use of a web or internet(503). Once on the site, the web server application prompts the user toidentify him or her with a secure password and username (507). Thisinitial step is a key component of the User and Organization PermissionComponent (504). If the information entered is incorrect, the user willbe denied access to the web server application. The AuthenticationFunction (508) is a key component of the User and OrganizationPermission Component. Once the user information provided has beenauthenticated, the User and Organization Permission Component assessesthe user's access to the site through the Authorization Function (509).This function is essential in defining the user's ability to operate andaccess the different components of the web server application. The AddUser Module (FIG. 12) and User Access Defining Module (FIG. 13) are thetwo modules controlling these first two steps. It is critical to realizethat only specific Authorized Users (510) have the ability to add ordelete accounts under their direct responsibility. The dashes in FIG. 5illustrate control links exerted by the Authorization Function (509) inthe User and Organization Permission Component (504). In addition to theUser Adding Module (FIG. 14) and the User Access Defining Module (FIG.15), the Authorized User will have access to four other modules. Thefirst is the Add and Edit Organization Module (FIG. 12). The second isthe Organization Listing module (FIG. 13). The third is the Organizationspecific User Listing Module (FIG. 16), which will enable the AuthorizedUser (510) to view all users for which they are authorized to edit anddelete the account. The fourth is the Organization User Editing Module(FIG. 17) which allows the Authorized User (510) to edit and update userinformation.

Note that the screens for the Edit Organization Module (FIG. 12), theOrganization Listing Module (FIG. 13), the User Listing Module (FIG.16), the Organization User Editing Module (FIG. 17), and other modulesin the system described here are form-based. By this, we mean that thereare specified areas for data entry, such as checkboxes and or finabletext fields. There can be a cursor on these screens that moves to thenext data entry area (i.e. box to be filled in). In some systems, theboxes to be filled in might be highlighted to make it clear to the userwhere the data is to be inserted. There can be a button that the userclicks when the information is to be processed, such as the submitbutton show at 1204 in FIG. 12) or the information can be processed asit is entered into each specified area for data entry, or when thecursor moves to the next data entry field. The form-based screens of thetype shown here can also have functionality to check that data beingentered is sensible before allowing the user to move to the next dataentry field. Such a form-based user-configurable system (also sometimesreferred to as a template-based system) makes it much easier to guide auser through the tasks needed to manage processing plant informationwithout the user needing to write computer code. In this way, theprocessing plant or plants can be defined; data can be logged; andreports and/or charts can be generated without requiring any custom codefor a specific plant or set of plants belonging to an organization.

For all examples, the edit modules emulate the ‘add new’ modules in thatboth display identical fields. However, the edit modules areself-populated by the data displacement element allowing the user toedit and update information in each field before saving modificationsinto the database by clicking the Save or Submit button.

Once the user has been authenticated and authorized access to the webserver application, the User and Organization Permission Component setsUser Access Filters (511) for each one of the remaining five components(512, 513, 514, 515 and 516). On the initial user login command, the webserver application will automatically access the User Home PageComponent (522) and provide the user with a page display response (523)that could be either the default view, which is the User Home PageSelection Module (FIG. 99) or the personalized user dashboard view setby the user in the Dashboard Management Modules (FIGS. 104,105, 106 and107).

When the first screen is displayed, the user will view relevant keyinformation and will be able to access all user home pagefunctionalities and web server application components using thenavigation links displayed on the screen by simply clicking the relevantlink. Hence if the user is looking to access the Define Component of aspecific facility, the user will click on the Define Component link. Theaccess request signal is sent to the web server application through theweb (503). Within the User and Organization Permission Component, therequest is redirected (524) to the appropriate user access filter (511),which in this case would be the Define User Access filter (513). If theuser is authorized to access the Define Component (519), the userdisplay message sent by the web server application back to the user willbe the Define Component/Plant Selection/Plant Listing and SelectionModules (FIG. 30), which will only display those facilities for whichthe user has access in the Define Component. If the user is notauthorized to access the Define Component, the web server applicationwill display a denial message using the page display (523) and give theoption to the user to access other components.

The number of cycles and combination can be extensive depending on thenumber of facilities managed by the web server application and thenumber of users within the specified organization. Under the presentconfiguration the system disclosed here provides its users with a secureplatform where all key operational data can be stored, accessed andanalyzed. Data stored can be as numeric and text-based values. Thesystem disclosed here also provides the ability to store files, images,documents of all formats, which can be accessed by authorized andauthenticated users.

In conclusion, the User and Organization Permission Component in FIG. 5is a key component of the security and information management of the webserver application. All tasks and requests are channeled through theuser access filters, which in turn can be modified at any time byAuthorized Users, through a series of clicks. The following paragraphswill now focus on the remaining five components.

FIG. 6 is a flowchart identifying the different functionalities andmodules in the Administer Component (601). The purpose of the AdministerComponent is to provide Authorized Users within the specifiedorganization with the ability to (a) add, list and edit plants orfacilities under the Plant Manager Function (602), (b) add, list andedit global parameters under the Global Parameter Manager Function(603), (c) add, list and edit global tasks under the Global Task ManagerFunction (604), and (d) add, list and edit links and files under theOrganization Links and Files Manager Function (605). The componentcomprises a total of 12 modules, which can be grouped differently.Screen displays of these modules can be viewed in FIGS. 18 through 29.

As it was presented in FIG. 1 and FIG. 5, the Administer Component isrelated to all of the other components within a specific organizationalaccount. For example a new facility can be created using the modulesunder the Plant Manager Function (602) through the Add, List, and EditPlant Modules . . . . Global or organization wide parameters are managedunder the Global Parameter Manager Function (603) through the Add, List,and Edit Global Parameter Modules.

FIG. 7 is a flowchart identifying the different functionalities andmodules in the Define Component (701). When accessing this component,Authorized Users within the specified organization are prompted to theDefine Component Plant Selection Module (702). Under the User andOrganization Permission Component configuration, the Authorized Userwill only be prompted to those facilities to which the user has access.

The purpose of the Define Component is to organize and identify all keyinformation that will be used by the web server application to organizethe database. The information captured can be grouped into two largecategories: operational and managerial. Under the operational categoryare functionalities and modules required to manage plant data and plantinformation, which are comprised of (a) the Add, List and Edit PlantParameter Modules under the Parameter Manager Function (703), (b) theAdd, List and Edit Plant Chemical Modules under the Chemical ManagerFunction (704), (c) the Add, List and Edit Plant Process Modules underthe Process Manager Function (705), (d) the Add, List and Edit PlantProcess Stream Modules under the Process Stream Manager Function (706),(e) the Add, List and Edit Plant Sampling Point Modules under theSampling Point Manager Function (707), and the Add, List and Edit PlantIssue Type Modules under the Issue Type Manager Function (708).

FIG. 7 illustrates how the different plant components fit together. Thisclassification is a core contribution to the computer based applicationdata management architecture. The Define Component user is able todefine, review or edit all key components and parameters. The onlyfunction not discussed in FIG. 8 is the Issue Type Manager Function.Using this function, the Plant Manager can track non-conventionaloperating parameters such as energy consumption, maintenance cost or anyother parameter which do not fall under the other more conventionalphysical-chemical parameters. Screen displays of these modules can beviewed in FIGS. 31 through 48.

The second category identified above includes all functionalities andmodules required to actively manage the facility which includes (a) theAdd, List and Edit Plant Notification Modules under the NotificationManager Function (709), (b) the Add, List and Edit Plant NotificationModules under the Task Manager Function (710), ands the Add, List andEdit Plant Action Modules under the Plant Action Manager Function (711).

Plant notifications are messages automatically generated by the systemdisclosed here. In the Define Component, the Authorized User defines thetriggers and the recipient of the notification. Under the Task ManagerFunction, the Authorized User builds a list of tasks which are thenintegrated under the Action Manager Function (711). The combination ofthese two functionalities provides the system disclosed here with abasic yet valuable workflow management tool. Similarly to theNotification Manager Function, the Action Manager Function issuesmessages to target users who may become accountable in the organization.

FIG. 8 is a diagram that depicts a generic elemental treatment orprocess facility (801) such as a drinking water treatment plant or achemical plant. The plant consists of a collection of processes (803,804, 806) and receives inputs in the form of raw materials (802) to beprocessed, and produces outputs (807) such as finished product. Thegeneral flow of the plant can be established as the inputs received tothe plant are transformed in each process.

The system disclosed here provides a method to define such a plant byallowing an end-user such as a Plant Manager to create a plant projectin a computer-based medium. Once the project is created, the methodallows for creation of unit processes, which can be a multi-stageprocess (803, 804) or a single stage process (806), and furtherassociate the unit processes to the newly created plant. By providinginformation on processes such as their placement order in the plant, thesystem disclosed here creates a computer embodiment of the actual plant,thus illustrating the actual placement of processes in the plant.

In addition to the processes, a plant also contains process streams(805) that carry material to and from the process. The raw material istypically carried to the first process in the plant, and the finishedmaterial after transformation exits from the last process in the plant.Each process can receive one or more streams, and also generate one ormore streams that may either enter another process or be discarded orused as waste material or as a potential product. By providinginformation on process streams such as their upstream and downstreamprocess and other details, the system disclosed here creates a computerembodiment of the actual plant, illustrating the actual flow of materialin the plant.

The system disclosed here allows the user to define the type ofinformation that is logged during the normal operation of a plant. Theseinclude flow, temperature and other information that describe theprocess or process stream. The approach provides a method to set thescope of the parameters, thus limiting or expanding the use ofparameters to the plant, processes and process streams. By providinginformation on parameters, the system disclosed here creates a computerembodiment of the actual plant, illustrating the actual monitoring ofthe transformation of material as it moves through the plant.

The system disclosed here also allows the user to define the type ofchemicals (809) that are used during the normal operation of a plant.These include chemicals that are added to processes and process streamsin order to alter the chemical behavior of material to improveefficiency of plant production. The approach provides a method to setthe scope of the chemicals, thus limiting or expanding the use ofchemicals in certain processes and process streams. The system disclosedhere provides information on the chemicals and monitors the actualtransformation of material as it moves through a plant where additionalchemicals are used.

Sampling points (808) that are points outside or inside the plantboundaries can also be defined in the system disclosed here. Samplingpoints are used to monitor a specific point that can be subject tocross-utility analysis or that may be critical from an operational,regulatory or management point of view.

FIGS. 30 through 57 are sample screenshots of the system disclosed here,providing additional information on how to define key components of theplant.

Once the Authorized User has defined the plant, its processes, processstreams, parameters and chemicals, and establish the scope of howparameters are monitored and chemicals used, operational information canbe collected and stored in the database. Individual plant users or thirdparty service providers can store data, automatically, manually orsemi-manually through a type of data upload process.

FIG. 9 is a flowchart identifying the different functionalities andmodules in the Data Logging Component (901). When accessing thiscomponent, Authorized Users within the specified organization areprompted to the Data Logging Component Plant Selection Module (902). ThePlant Selection Module will only display those plants or facilities towhich a user has access. Those permissions are set in the User andOrganization Permission Component.

The purpose of the Data Logging Component is to capture the informationand data viewed as critical for the Plant or Area Manager. Under thesystem disclosed here, the Plant Manager can log operational informationin various formats such as numeric; text-based, audio or visualinformation. The Plant Manager also has the ability to attach otherrelevant computer files, such as documents and spreadsheets. The systemdisclosed here is able to accept data from a wide range of sources. Forexample, data can be captured on site by the operator or by usingon-line monitors. Data can also be imported using off-site sources suchas laboratories or data upload. At all times, Authorized Users canreview and edit the data. Any changes made to the data are recorded bythe system disclosed here and can be reviewed by the Administrator orthe Super Administrator.

Among the key functionalities and modules associated with the DataLogging Component are (a) the Add, List and Edit Plant Log Modules underthe Plant Log Manager Function (903), (b) the Add, List and Edit ProcessLog Modules under the Process Log Manager Function (904), (c) the Add,List and Edit Process Stream Log Modules under the Process Stream LogManager Function (905), (d) The Add, List and Edit Sampling Point LogModules under the Sampling Point Log Manager Function (906), and (e) theAdd, List and Edit Plant Issue Log Modules under the Plant Issue LogManager Function (907).

The terms Plant Log, Process Log, Process Stream Log, and Sampling PointLog used in the previous paragraph are referenced in FIG. 8 andavailable in Define Component. Additional information regarding thedifferent modules under the Data Logging Component is provided in FIGS.58 through 73.

Once data has been stored in the database, the Authorized User is ableto run queries on these data and produce reports and charts. Anotheroption is to integrate the information into pre-defined models or forms,which would have been approved by the Super Administrator or theAdministrator. The approach allows for individual plant users or thirdparty service providers to access the data, automatically, manually orsemi-manually by using pre-developed reports or queries.

FIG. 10 is a flowchart identifying the different functionalities andmodules under the Data Reporting Component (1001). When accessing thisComponent, Authorized Users are prompted to the Data Reporting ComponentPlant Selection Module (1002). The Authorized User within the specifiedorganization will only be prompted to those facilities to which the userhas access as defined in the User and Organization Permission Component.

The purpose of the Data Reporting Component is to allow Plant Managersand Area Managers to meet their reporting requirements using thedifferent functionalities made available by the system disclosed here.In order to meet the reporting needs of both Plant Managers and AreaManagers, the key functionalities and modules associated with the DataReporting Component were divided into two large categories:plant-specific functions and cross-facility functions.

The plant-specific functions identify those functions and modules thatallow the Plant Manager to focus on plant data. The modules listed inFIG. 10 include the following (a) Create, List, Generate and PublishReport Modules under the Plant Report Manager Function (1003), (b)Create, List, Generate and Publish Chart Modules under the Plant ChartManager Function (1004), (c) Add, List, Run and Publish Plant ModelModules under the Plant-Specific Model Manager Function (1005), and (d)Add, List, Run and Publish Plant Form Modules under the Plant-SpecificForm Manager Function (1005).

The cross-facility functions offer global parameters to allow the AreaManager to perform trending analysis across several facilities. Themodules listed under FIG. 10 include the following (a) Create, List,Generate and Publish Report Modules in the Global Report ManagerFunction (1008) and (b) Create, List, Generate and Publish Chart Modulesin the Global Chart Manager Function (1009).

Additional information regarding the different modules under the DataReporting Component is provided in FIGS. 74 through 98.

The last Component is the User Home Page Component. The User Home PageComponent is the only Component that all users within the givenorganization have access to. This Component allows the user to focus onwhat is essential to perform his/her duty. Hence it is through the UserHome Page Component that notifications and action lists are displayed.The web server application can also issue notifications to e-mailaddresses. The User Home Page Component also enables the user to viewkey information and update personal information when needed.

FIG. 11 is a flowchart identifying the different functionalities andmodules under the User Home Page Component (1101). When accessing thisComponent, Authorized Users are prompted to the User Home Page ComponentPlant Selection Module (1102). The Authorized User within the specifiedorganization will only be able to view those facilities to which theuser has access as set in the User and Organization Permission Componentconfiguration. By selecting a plant, the user will be prompted to theWorkflow Manager Function (1103), which is composed of four key modules(a) the User Specific Notification Listing and Selection Module, (b) theUser Specific Plant Action Listing Module, (c) the Action SpecificDescription Module, and (d) the Task Description Module.

The remaining three functionalities relate to user-specific information.First, the Dashboard Manager Function (1105) relates to criticalinformation that the user needs to track. The Dashboard Manager Functionis formed of four modules (a) the Home Page Set Up Module, (b) DashboardData Selection Module, (c) Chart Selection Module, and (d) Pre-set FileModule. The second function is the Personal Profile Manager Function(1106), which enables the user to update his or her informationincluding the password set in the User and Organization PermissionComponent. The two modules that form this function are the User ProfileViewing and Editing Module and the User Profile Site Access ViewingModule.

The final function is the General Information Manager Function (1107).Through this function, the user can communicate to the organization andreceive messages from the organization. This function is formed of threemodules. The first two are the Bulletin Board Posting Module and theBulletin Board Response Module . . . . The last module is the FileDownload and Link Access Module, which enables the user to downloadfiles or access links.

Additional information regarding the different modules under the UserHome Page Component is provided in FIGS. 99 through 112.

The following sections describe the individual modules associated withthe Components and functions presented in FIG. 1.

2—User and Organization Permission Component

The User and Organization Permission Component determines access to theapplication. The component utilizes a dual method of authentication andauthorization to verify user access and provide the user access to theweb server application. Simultaneously, Authorized Users within thespecified organization have the ability to create Organization and Useraccounts. The following six modules are only accessible to the SystemAdministrator, while the Super Administrator, the Administrator, theArea Manger and the Plant Manger will have the ability to add, list andedit new user accounts within the confines of their Organizationalaccount.

The six modules in the User and Organization Permission Component areonly accessible for Authorized Users. FIGS. 12 through 17 arescreenshots of the six modules and are as follow: Add and EditOrganization (FIG. 12). Organization Listing (FIG. 13), Add User (FIG.14), User Access Permission (FIG. 15), User Listing (FIG. 16), and UserEdit (FIG. 17). By clicking on the component, a menu will appear withthe linked modules, which are then each accessed by clicking on theindividual module button.

The organization definition module is comprised of, but not limited to,a plant listing module and a users listing module. Under the systemdisclosed here, the users listing module is responsive to both a userdefinition module (add/edit) and a user functions listing module.

The process begins with the Authorized User creating a new organizationaccount (FIG. 12). Connecting to the internet or intranet, the SystemAdministrator accesses the form-driven user configurable computerimplemented solution and clicks on the Organization and User Access tab,which will enable the user to view all the options he/she has access to.The user then clicks on the Add/Edit New Organization button on the leftside of the screen (1201) and is provided with a self generated form(1202). This module defines the organization. The input fields (1202)are for organization name, organization contact person name, which willalso be the Super Administrator for the Organization, the organizationaddress, organization phone number, organization fax number,organization email address, and organization web address. Additionally,fields identifying the number of authorized plants and users areavailable for input. A comment or description may be added in theOrganization description field (1203). The Submit button (1204) isselected when input is complete. This save button is responsive to userinput, whereby the data movement element is capable of transferring theuser-provided contents to computer memory in response to a signal anddoes not require user-supplied computer code to transfer. At this point,a new organization is created and stored in the database.

FIG. 13 illustrates the screen display for the Organization Listingmodule or Organization module. This module is accessed by clicking onthe Organization button on the left side of the page (1301). This screendisplay allows the System Administrator to edit or delete a particularorganization's information. The self generated Organization Listingtable (1302) lists the organizations currently set up in the applicationorganized by name and particular details. Note that per the example, XYZCorporation (1303) has been added to the Organization Listing. ClickingEdit button (1304) launches the screen in FIG. 12, while clicking on thedelete button would delete the entry. Clicking the Edit button under thePlant List column (1305) will open the plant listing module for thatspecific organization (see FIG. 19), while clicking on the Edit buttonunder the User List column (1306) will open the user listing module forthat specific organization (see FIG. 16).

Once the Organization is created, the organization super administratoris able to create new users for that specific account. FIG. 14illustrates the screen display for Add User, where the Authorized Userinputs new user information; for this example, the new user is SamJones. To access this module the user clicks on Add User button (1401)on the left side of the screen and is provided with a self generatedform (1402). The fundamental input fields are user login name, loginpassword, contact, location address, phone and fax numbers, and emailaddress. The Authorized User is able to define the user's access to thedifferent modules of the application by clicking on User AccessDefinition (1403). Once the input is complete, the Authorized Userselects the Submit button (1404) to transfer the data to the database byuse of a data transfer element.

Clicking User Access Definition button (1403) opens a window andactivates the user functions listing module. Illustrated in FIG. 15,User Access Permission (1501) is where the Authorized User configurescomponent module permission for a new user, one plant at a time, underthe specified organization account. Under the User Information Table(1502), the system disclosed here confirms the user's name for which theAuthorized User is defining the web server user access. In the case ofthe example presented in FIG. 15, the name of Sam Jones is confirmed.

To select the plants that the user will have access to, a selection willbe made from the Plant Selection drop-down menu (1503). The content inthe drop-down menu will be determined by the Authorized User, who willalso determine the number of facilities that the user will have accessto. For example, if the system was set for three plants (#1, #2, #3),and the Authorized User was an Administrator, the Plant Selectiondrop-down menu would offer four choices: Plant #1, Plant #2, Plant #3,or All. In the example, the Authorized User selected Plant #1. If theAuthorized User accessing this window was the Plant Manger of Plant #1,the Plant Selection drop-down menu would contain only one choice: Plant#1. This adjustment is performed by the computer-implemented applicationthrough the User and Organization Permission Component AuthorizationModule.

To define Sam Jones's access level, the Authorized User has access tothe Access Level drop-down menu (1504); the choices under this drop-downare dependent on the Authorized User access. In the case of anAdministrator, the drop-down menu will offer five choices: Area Manager,Plant Manager, Superintendent, Operator or External User. In the casewhere the Area Manger is the Authorized User, the choices under thedrop-down menu would be Plant Manager, Superintendent, Operator orExternal User. In the case illustrated in FIG. 15, the selectedAuthorized User level was set to Plant Manager. As a result of thischoice the system disclosed here auto-populated the User Accessrequirements (1505) to match those of a Plant Manger, as defined in FIG.4; the radio boxes being marked accordingly by the system's displayelement.

Some Authorized Users, such as Area Manager or Plant Manager, have theability to override another user's access whenever warranted. Thisflexibility is particularly important in the case of an External User.The Authorized User may select to give access to all modules, access tospecific modules or View-only rights. In this example, since a PlantManager can create new user accounts, Add/Edit User Accounts (1506) isselected in FIG. 15. The content of the drop-down menu identified by thetriangle at the right of the box will include a suite of user typesconsistent with the Authorized User's access.

The Define (1508), Data Logging (1509), and Data Reporting (1510)Modules have been selected, as indicated by the checked radio boxes nextto the fields in FIG. 15. The choices in the corresponding drop-downmenu are Add, List, Edit, or All modules. The Administer ComponentModules (1511) have not been selected as indicated by the empty radiobox because of the user's access level. In this case, Global TaskManager Function, Announcement Manager Function, Plant Manager Function,Global Parameter Function, and Links and Files Manager Function andtheir corresponding modules of Add, List, Edit, or All (function)modules would not be accessible to the user. The second column presentsthe View only for the all or any of the components. If the View onlycells were selected by the Authorized User for the Define modules Viewonly (1512) Data Logging Modules View only (1513), and Data ReportingModules View only (1514), the choices in the drop-down menus would beAdd, List, Edit, or All (Component) modules View only. The AdministerModules View only (1515) was selected, so the user is able to review allinformation in the Global Task Manager Function, Announcement ManagerFunction, Plant Manager Function, Global Parameter Function, and Linksand Files Manager Function, but unable to add or modify any information.Clicking Submit button (1516) saves these settings, closes the windowand returns to previous page in FIG. 14. In FIG. 14, Submit button(1404) is selected to save all input.

To provide access to another plant for this specific user account, theAuthorized User would click a second time on the User Access DefinitionButton (1403) in FIG. 14, which in turn would open the User AccessDefinition Window (FIG. 15).

To access all users enrolled in the application for the organization'saccount, Search/List Users is required. FIG. 16 illustrates the screendisplay for Search/List Users (1601), which enables the Authorized Userto review, edit or delete existing user information. This page isaccessed by clicking on Search/List Users button on the left side of thepage (1601). The User Listing table (1602) lists the users currentlypermitted to utilize the application organized by name and particulardetails. Based on the example above, Sam Jones (1603) has been added tothe User Listing. Upon selecting Edit button (1604) from table, theAuthorized User will be prompted to FIG. 17. FIG. 17 illustrates thescreen display for Edit Users (1701), where the Authorized User ispermitted to update general information (1702) and modify or update theuser's application access (1703). The latest changes are loggedidentifying the name of editor and the date last modified (1704).Changes are saved upon selecting Submit button (1705).

Individual users are able to update their personal information throughthe Home Page Component (see FIG. 108).

3—Administer Component

The Administer Component establishes the specified organization'sstructure for their facilities. There are five functions in theAdminister Component that are only accessible for Authorized Userswithin the specified organization. The functions are comprised of, butnot limited, to 3 modules and are presented in the following figures asscreenshots of the Administer Component. The function and modules are asfollow: Plant Manager Function Modules are Plant Adding (FIG. 18), PlantListing (FIG. 19), and Plant Editing (FIG. 20); Global ParameterFunction Modules are Global Parameter Adding (FIG. 21), Global ParameterListing (FIG. 22), and Global Parameter Editing (FIG. 23); Global TaskManager Function Modules are Global Task Adding (FIG. 24), Global TaskListing (FIG. 25), and Global Task Editing (FIG. 26); Links and FilesManager Function Modules are Links and Files Adding (FIG. 27), Links andFiles Listing (FIG. 28), and Links and Files Editing (FIG. 29). Byclicking on the component, a menu will appear with the linked modules,which are then each accessed by clicking on the individual modulebutton. Utilizing the system disclosed here; Authorized Users are ableto set-up individual facilities under their organization and have theability to assign specific managerial attributes for all facilities. TheAdminister Component can be used as a source for providing guidelinesand tools for users to utilize for the tracking of pertinent data.

The process begins with the creation of a new plant for theorganization. Authorized Users are provided with three options tonavigate to the configuration page for a new plant. The first option isthrough the Define Component, which will be described in the followingsection. The second and third options are through the AdministerComponent in the Add New Plant Listing Module and the Plant ListingModule. FIG. 18 illustrates the screen display for Add New Plant Listing(1801) which enables the Authorized User to input new plant informationinto the application; Plant #3 is the example. The user clicks on theAdd New Plant Listing button on the left side of the screen (1801) andis provided with a self generated form (1802). Particular field input onthe form displayed will be required such as plant name, plant locationaddress, plant phone and fax numbers, plant email and web addresses, andthe plant contact person's name. Also default parameter fields requireinput for the new plant. These default parameters consist of plant flowunit, plant pressure unit, plant temperature unit, and the plant startdate and history. This data is the predefined plant parameters utilizedin the next sections. A comment or description may be added in the PlantDescription field (1803). The Submit button (1804) is selected wheninput is complete. At that time, a new facility is created and stored inthe database. FIG. 19 illustrates the screen display for Plant Listing(1901). This screen allows the user to review, edit or delete existingplant information. This page is accessed by clicking on the PlantListing button on the left of the page (1901). The Plant Listing table(1902) lists the plants currently set up in the application for aspecific organization by name and particular details. Note that per theexample, Plant #3 (1903) has been added to the Plant Listing. A map(1904) provides the geographic location of all facilities. With theentry of the new plant, Plant #3, its location is pinpointed on the map(1905), which is auto populated by the system's display element. Theuser may click the Create New Plant button (1906) to add another plantunder the same organization. This selection will navigate the user toFIG. 18, Add New Plant Listing to configure a new plant.

Clicking Edit button (1907) launches the screen in FIG. 20. This screen,Plant Details (2001), is where the Authorized User is permitted toupdate plant information in the Plant Details table (2002) and in thePlant Description field (2003) when warranted.

The latest changes are logged identifying the name of the editor and thedate last modified (2004). Selecting Submit button (2005) saves thecompleted changes and transfers the data to the database by use of adata transfer element.

FIG. 21 illustrates the screen display for Add Global Parameter, wherethe Authorized User sets new global parameters (2102), which areparameters that will be measured for all facilities within theorganization. This module is a key feature in the organizationdefinition module. Furthermore, this feature is also linked to the plantdefinition module, and the Log and Reporting Components. To access thismodule the user clicks on the Add Global Parameter button on the leftside of the screen (2101) and is provided with a self generated form(2102). The form displayed will require input in the fields of theparameter name, type, units, minimum and maximum values, enforce minimumand maximum values, and any special operand. This data will be utilizedin the next sections for the predefined organization parameters. Theexample of global parameter used in FIG. 21 is plant energy usage. Whendefining the Global Parameter the user will need to define two keycriteria (1) the system type (2103) and (2) the units (2104). The Typefield (2105) is a drop-down menu which provides the user with a choiceof 5 options for the application. The Global Parameter could be appliedto one of the following: at plant level, at process level, at processstream level, as an issue type or as a specific predefined samplingpoint; the user must select one of these 5 options.

In the example presented in FIG. 21, the new global parameter beingintroduced into the system is named “Energy usage”; the parameter willapply at the plant level and the units which are manually introduced arekW/day. To add further information on the Global Parameter beingcreated, a Description field (2106) can be used. Click Submit button(2107) when input is complete.

FIG. 22 illustrates the screen for Global Parameter Listing module,which enables the Authorized User option to review, edit or deleteexisting organization parameters. This module is accessed by clicking onthe Global Parameter Listing button on the left side of the page (2201).Global Parameters table (2202) lists the current organization parametersutilized for all facilities by name and description. Note that per theexample, a new parameter, Energy usage (2203), has been added to theGlobal Parameter Listing. Selecting Edit button (2204) launches the EditGlobal Parameter screen as illustrated in FIG. 23. On the Edit GlobalParameter screen (2301), the Authorized User is permitted to update theDefinition (2302) and the Description field (2303) when required. Thelatest changes are logged in Last Edit Track and identify the name ofeditor and the date last modified (2304). Changes are saved when Submitbutton (2305) is selected.

FIG. 24 illustrates the screen display for Add Global Task, where theAuthorized User assigns a new multi-facility task to be completed in thecase of an event. The user clicks on the Add Global Task button on theleft side of the screen (2401) and is provided with a self generatedform (2402). Whereas a task can be defined for a specific facility inthe Define Component, the Global Task is for several facilities within aspecified organization. The information displayed can include, forexample, a title and a contact name (2402) and a brief description ofthe task (2403) with the opportunity to add reference documents or links(2404) to assist the operator in completing the task. In FIG. 24, theexample displays a task titled EPA Task 101 and the contact name is SamJones. Submit button (2405) is selected when input is complete. FIG. 25illustrates the screen display for Global Task Listing (2501), whichprovides the Authorized User option to review, edit or delete existingmulti-facility tasks. This page is accessed by clicking on the GlobalTask Listing button on the left side of the page (2501).

The Global Task Listing table (2502) lists the global tasks currentlyassigned for all facilities within a specified organization by name andparticular details. Based on the example above, EPA Task 101 and SamJones have been added to the Global Task Listing (2503). Selecting Editbutton (2504) launches the Global Task screen, as illustrated in FIG.26. In the Global Task screen (2601), the Authorized User is permittedto update Task Requirements (2602) and the Description (2603) asnecessary. Any documents or links related to the particular task can beuploaded or attached (2604). The latest changes are logged and displayedin Last Edit Track, which identifies the name of editor and the datelast modified (2605). Selecting Submit button (2606) saves any changes.

FIG. 27 illustrates the screen display for Add Files and Links, whichgives the Authorized User the ability to upload documents and attachlinks applicable to the facility or the organization which manages thefacility. Once uploaded, these documents will be visible by all users.The user clicks on the Add Files and Links button on the left side ofthe screen (2701) and is provided with a self generated form (2702). Fordocument upload, a range of file types are available in the Select FileType drop-down menu (2703): pdf format, Word documents, text files,image, and video. Excel (2702) is used as an example in FIG. 27. Oncethe file type is selected, the user can provide additional informationon the file by using the Description text field (2704). Upload button(2705) is selected to execute. To link an attachment, both name and pathare typed in the Name and Link Path fields (2706), respectively. Thelink, www.newlink.com, is the example in FIG. 27. A description orcomment may be typed in the Description text field (2707). Attach button(2708) is selected to attach the link. Clicking Submit button (2709)saves changes this screen.

FIG. 28 illustrates the screen display for Files and Links Listing,which enables the Authorized User option to view, download or deletefiles and attach or delete links. This page is accessed by clicking onthe Files and Links Listing button on the left side of the page (2801).The Files available for download table (2802) lists files available fordownload, while the Attached links table (2803) lists available linksmaintained in the application for a specified organization by name andparticular details. Note that per the example, the Excel document (2804)and EPA link (2805) have been added to the Files and Links Listing.Selecting Edit (2806) in either table launched the Edit Files and Linksscreen, illustrated in FIG. 29. On the Edit Files and Links screen(2901), the Authorized User is permitted to update files and linkinformation Definition (2902) and Description (2903) when required. Tochange a link, the user may click Attach button (2904). The latestchanges are logged and displayed in the Last Edit Track table, whichidentifies the name of editor and the date last modified (2905). Changesare saved when Submit button (2906) is selected.

4—Define Component

The Define Component identifies the functional attributes for a specificfacility within the organization account. There are nine functions inthe Define Component that are only accessible for Authorized Users. Thefunctions are comprised of, but not limited, to 3 modules and areillustrated in the following figures. Parameter Manager Function modulesare Plant Parameter Adding (FIG. 31), Plant Parameter Listing (FIG. 32),and Plant Parameter Editing (FIG. 33). Chemical Manager Function Modulesare Plant Chemical Adding (FIG. 34), Plant Chemical Listing (FIG. 35),and Plant Chemical Editing (FIG. 36). Process Manager Function Modulesare Plant Process Adding (FIG. 37), Plant Process Listing (FIG. 38), andPlant Process Editing (FIG. 39). Process Stream Manager Function Modulesare Plant Process Stream Adding (FIG. 40), Plant Process Stream Listing(FIG. 41), and Plant Process Stream Editing (FIG. 42). Sampling PointManager Function Modules are Plant Sampling Point Adding (FIG. 43),Plant Sampling Point Listing (FIG. 44), and Plant Sampling Point Editing(FIG. 45). Issue Type Manager Function Modules are Plant Issue TypeAdding (FIG. 46), Plant Issue Type Listing (FIG. 47), and Plant IssueType Editing (FIG. 48). Notification Manager Function Modules are PlantNotification Adding (FIG. 49), Plant Notification Listing (FIG. 50), andPlant Notification Editing (FIG. 51). Task Manager Function Modules arePlant Task Adding (FIG. 52), Plant Task Listing (FIG. 53), and PlantTask Editing (FIG. 54). Actions Manager Function Modules are PlantAction Adding (FIG. 55), Plant Action Listing (FIG. 56), and PlantEditing (FIG. 57). By clicking on the component, a menu will appear withthe linked modules, which are then each accessed by clicking on theindividual module button. Utilizing the system disclosed here,Authorized Users are able to set up a facility with specific operativeand data requirements. The Define Component can be used to designatespecific factors to be identified and tracked by Authorized Users forpertinent data.

The plant definition module is comprised of, but not limited to, aparameter listing module and parameter definition module (add/edit), achemical listing module and chemical definition module (add/edit), aprocess listing module and process definition module (add/edit), aprocess stream listing module and process stream definition module(add/edit), and a sampling point listing module and sampling pointdefinition module (add/edit) under the system disclosed here.

The following figures will be using Plant #3 as an example of how anAuthorized Users uses the Define Component of the system disclosed here.FIG. 16 illustrates how Plant #3 was added to the system.

The process begins with selecting the plant that the Authorized Userwants to access. FIG. 30 illustrates the screen for the Plant Listingmodule (3001), part of the plant definition module under the form-drivenuser configurable computer implemented solution. The Plant Listingmodule enables the user to view and select facilities for which the userhas reading and/or writing rights as specified by the Authorized Userwithin the organization managing these systems. This page is accessed byclicking on the Plant Listing button on the left of the page (3001). ThePlant Listing and Selection table (3002) is a directory of the plantsand their assigned contacts. Clicking Select button (3003) allows theuser to review a plant's administrative and functional information andto define the plant's fundamentals. A map (3004) provides the geographiclocation of all facilities within a specified organization . . . .Specific information associated with the facility can be displayed fromthe map when the user clicks on the specific facility, which is autopopulated by the system's display element. The user may click the CreateNew Plant button (3005) to add another plant under the sameorganization. This selection will navigate the user to FIG. 18, Add NewPlant Listing in the Administer Component to configure a new plant.

FIG. 31 illustrates the screen for Add Parameter, where the user setsthe individual parameters to be measured or tracked for a facilitywithin a specified organization. Through this module, the user has theability to build its own library of parameters as needed. To access thismodule the user clicks on the Add Parameter button on the left side ofthe screen (3101) and is provided with a self generated form (3102). Inthis figure, a new parameter, TOC, is being added. Particular fieldinput on the form will be required, such as parameter name, type, units,minimum value, maximum value, enforce minimum and maximum value, and anyspecial operand. This data will be utilized in the next sections for thepredefined plant-specific parameters. The Definition table (3102) is anexample of the type of information that the system disclosed here willrequest. The user defines the name of the parameter, the units and theparameter type. The Type drop-down menu (3103) is significant as thisprovides the user with pre-set options defined by the system disclosedhere. The options under the Type drop-down menu are plant, process,process stream, sampling point, and issue type. In the case of thisexample, TOC will be applied as a sampling point parameter and isentered in the Description text field (3104). The Submit button (3105)is selected when input is complete.

FIG. 32 illustrates the screen for the Parameters Listing module,enables the user option to review, edit or delete an existing parameterfor a facility within a specified organization. This module is accessedby clicking on the Parameter List button on the left side of the page(3201). The table Plant Parameters (3202) lists the parameters currentlyutilized for Plant #3 by name and particular details. Note that per theexample, TOC (3203) has been added to the Parameter List. The Editbutton (3204) is active and the user will be able to edit this parameterimmediately even though it was just added to the list of parametersmonitored under Plant#3.

Selecting Edit button (3204) will launch the Edit Parameter screendisplayed in FIG. 33. In Edit Parameter (3301), the Authorized User ispermitted to update and modify Parameter Definition (3302) andDescription (3303) when required. The latest changes are logged anddisplayed in Last Edit Track, which identifies the name of editor andthe date last modified (3304). Changes are saved when Submit button(3305) is selected.

FIG. 34 illustrates the Add Chemical screen, where the user sets thechemicals to be utilized and measured for the selected facility within aspecified organization. To access this module, the user clicks on theAdd Chemical button on the left side of the screen (3401) and isprovided with a self generated form (3402). In the Definition table(3402), information relevant to the new chemical is required. Fieldinput on the form will be chemical name and type, as well as chemicaldosage, rate, loading and feed density units. This data will be thepredefined chemicals to be utilized in the next sections. In thisexample displayed in FIG. 34, chlorine is the new chemical being addedto the list of chemicals used at Plant#3. The Authorized User specifiesthe units being used for a variety of parameters which applies to thechemical. Additional comments may be entered into the Description textfield (3403). Submit button (3404) is selected when input is complete.

FIG. 35 illustrates the Chemical Listing module, which provides the userthe option to review, edit or delete an existing chemical for a facilitywithin a specified organization. This module is accessed by clicking onthe Chemical List button on the left side of the page (3501). The PlantChemicals table (3502) lists the chemicals currently utilized for Plant#3 by name and particular details. The new chemical that was added inFIG. 34, Chlorine (3503) has been added to the Chemical List. Selectingthe Edit button (3504) for Chlorine will allow the user to edit theinformation in FIG. 34 and will launch the Edit Chemical screendisplayed in FIG. 36. On the Edit Chemical screen (3601), the AuthorizedUser can update chemical Definition (3602) and Description (3603) whenrequired. The latest changes are logged identifying the name of editorand the date last modified (3604). Selecting Submit button (3605) saveschanges completed and updates the data storage component allocated forPlant#3 under the computer-implemented solution.

FIG. 37 illustrates the screen for Add Process, where the AuthorizedUser identifies the processes utilized at the facility within aspecified organization. To access this module the user clicks on the AddProcess button on the left side of the screen (3701) and is providedwith a self generated form (3702). The new Process Definition Table(3702) presented in FIG. 37 is comprised of three categories: the nameof the process, the number of stages in the process, and placement orderof the process in the treatment train. The field input on the form willbe process name, type, number of process stages, and process placementorder. This data will be utilized in the next sections for thepredefined process parameters. In the example given in FIG. 37, the useris adding a process called “Filter”, which is a single stage process andis placed third in the overall treatment scheme. Additional informationcan be entered into the Description text fields (3703). The Parameters(3704) and Chemicals (3705) are options made available to the user bythe system disclosed here once the parameters and chemicals were addedto the system as described by FIGS. 31 and 34. The process parameterslisting module and process chemicals listing module are activated todisplay the monitoring parameters and utilized chemicals in theoperation of the process. To select a parameter or chemical, theAuthorized User clicks the checkbox to the left of the correspondingitem. The Authorized User selected Alkalinity as a parameter to bemonitored for the new Filter process being added. The Submit button(3706) is selected when input is complete.

FIG. 38 illustrates the Process Listing module, which enables the userto review, edit or delete existing processes for a facility within aspecified organization. This module is accessed by clicking on theProcess List button on the left of the page (3801). The Plant Processestable (3802) lists the processes currently in the system for Plant #3 byname and particular details. Note that per the example described in theprevious paragraph for FIG. 37, Filter (3803) has been added to theProcess List. Selecting Edit button (3804) for the Filter launches theEdit Process screen (3901) as displayed in FIG. 39. In the Edit Processscreen, the Authorized User is permitted to update process Definition(3902) and Description (3903) when required. In this figure, thechemical Chlorine (3905) has been selected, in addition to the parameterAlkalinity (3904). By the utilization of checkboxes, parameters andchemicals can be added and removed directly. These two modules will betracked in the Data Logging Component of the system disclosed here.These changes are logged and displayed in the Last Edit Track, whichidentifies the name of editor and the date last modified (3906). Changesare saved upon selecting Submit button (3907).

FIG. 40 illustrates the screen for Add Process Stream, where theAuthorized User defines for the selected facility within a specifiedorganization a new process stream, which is the link between twoprocesses. To access this module the user clicks on the Add ProcessStream button on the left side of the screen (4001) and is provided witha self generated form (4002). The field input on the form will beprocess stream name, code, type, upstream process and downstreamprocess. This data will be the predefined chemicals to be utilized inthe next sections. In the sample Definition table (4002), the AuthorizedUser has the ability to define the new process stream through a seriesof descriptors, which include a) the name of the process stream, b) theprocess stream type, c) the upstream process and d) the downstreamprocess. Corresponding drop-down menus (4003, 4004, and 4005) areavailable for the different descriptors. The Type drop-down menu (4003)is predefined by the system disclosed here which includes types such asfeed, product, recycle, regular, waste and by-pass. The Upstreamdrop-down menu (4004) and the Downstream drop-down menu (4005) list theprocesses which currently exist in the system. The processes are Filterand Tank as defined in the example of FIG. 37. In the case presented inFIG. 40, the process stream that is being created between the Tank andthe Filter is named Filter Feed (4006). Additional comments may beentered in the Description text field (4007). The listed Parameters(4008) and Chemicals (4009) were predefined under the Add Chemical andAdd Parameter sections and are the product of the logic operating in thesystem disclosed here. The process stream parameters listing module andprocess stream chemicals listing module are activated to display themonitoring parameters and utilized chemicals in the operation of theprocess stream. The Authorized User can select the chemical or theparameter by clicking on the checkbox to the left of the desiredchemical or parameter. In FIG. 40, the user selected Alum, suggestingthat Alum is being added to the Filter Feed stream. The Submit button(4010) is selected when input is complete.

FIG. 41 illustrates the screen for Process Stream Listing Module, whichenables the user option to review, edit or delete the existing processstreams in the system for a facility within a specified organization.This module is accessed by clicking on the Process Stream List button onthe left of the page (4101). The Plant Process Stream table (4102) liststhe process streams currently utilized for Plant #3 by name andparticular details. The new process, Filter Feed (4103), added in FIG.40, is now displayed in the Process Stream List. Selecting Edit button(4104) for Filter Feed launches the Edit Process Stream, displayed inFIG. 42. In the Edit Process Stream (4201), the Authorized User is ableto update Process Stream Definition (4202) and Description (4203). Inthis example parameter TOC (4204) and chemical chlorine (4205) have beenselected as the attributes to the process steam of filter feed. By theutilization of checkboxes, parameters and chemicals can be added orremoved directly. The latest changes are logged in Last Edit Track,which identifies the name of editor and the date last modified (4206).Changes are saved when Submit button (4207) is selected.

FIG. 43 illustrates the screen display for Add Sampling Point, where theuser defines the descriptors for a given sampling points, which can beany point within or outside the selected facility within a specifiedorganization. A sampling point does not need to be attached to a processor process stream. To access this module the user clicks on the AddSampling Point button on the left side of the screen (4301) and isprovided with a self generated form (4302). The field input on the formwill be sampling point name, code, and type. This data will be thepredefined sampling points to be utilized in the next sections. Theinformation displayed in the sample Definition table (4302) shows twodescriptors: the name, Lake Intake, and a code or reference number“0110”. Additional comments can be entered in the Description text field(4303). The Parameters (4304) linked to the facility are provided, sothat the user may assign the attributes to the sampling point ifapplicable; in FIG. 43, no parameter has been selected. The listing ofpredefined parameters is a function of the parameters that were added inthe system under the Add Parameter Module of the system disclosed here.The sampling point parameters listing module is activated to display themonitoring parameters for the sampling point. The Submit button (4305)is selected when input is complete.

FIG. 44 illustrates the Sampling Point Listing Module, which enables theuser option to review, edit or delete all existing sampling points for afacility within a specified organization. This module is accessed byclicking on the Sampling Point List button on the left side of the page(4401). The Plant Sampling Point table (4402) lists the sampling pointscurrently in the system for Plant #3 by name and particular details.Note that per the example in FIG. 43, Lake Intake (4403) has been addedto the Sampling Point List. Clicking Edit button (4404) launches theEdit Sampling Point screen as illustrated by FIG. 45.

On the Edit Sampling Point screen (4501), the Authorized User ispermitted to update sampling point Definition (4502) and Description(4503) when required. In this example, the Parameter Turbidity (4504)has been selected as the attribute to the sampling point. By theutilization of checkboxes, parameters and chemicals can be added andremoved directly. The latest changes are logged and displayed in theLast Edit Track, which identifies the name of editor and the date lastmodified (4505). Selecting Submit button (4506) saves changes.

FIG. 46 illustrates the screen for Add Issue Type, where the user setsissue types to be reported at a specific facility within anorganization. To access this module the user clicks on the Add Issuebutton on the left side of the screen (4601) and is provided with a selfgenerated form (4602). The Definition table (4602) consists of a fieldwhere the Authorized User can add the name of the issue type beingtracked; in this example, pH alert is the issue type that is displayed.Additional comments are entered in the Description text field (4603).The issue parameters (4604) available in the system for this specificplant are presented so that the user may assign the attributes to theissue type if applicable; in this case no parameter has been selected.The Submit button (4605) is selected when input is complete.

FIG. 47 illustrates the Issue Type List screen, which enables the userto review, edit or delete existing issue types for a facility within aspecified organization. This module is accessed by clicking on the IssueType List button on the left side of the page (4701). The Plant IssueTypes table (4702) lists the issue types currently utilized for Plant #3name and particular details. The new Issue Type, pH Alert (4703) hasbeen added to the Issue Type List. Selecting Edit button (4704) for thepH Alert launches the Edit Issue Type screen as displayed in FIG. 48.The Edit Issue Type screen (4801), where the user is permitted to updateIssue Type Definition (4802), Description (4803), and Parameters (4804)when required. In this example parameter pH Alert (4805), has beenselected as the attribute to the issue type. The latest changes arelogged and displayed in Last Edit Track and identifies the name ofeditor and the date last modified (4806). Changes are saved uponselecting Submit button (4807).

FIG. 49 illustrates the Add Notification screen, which allows theAuthorized User to set automatic notifications to identified users as afollow-up of specific triggers for the selected facility within aspecified organization. The logic behind the system disclosed hereenables the Authorized Users to drill down to one or several parameters.In FIG. 49, the Authorized User is setting a notification on the pHalert issue that was defined in FIG. 46. To access this module the userclicks on the Add Notification button on the left side of the screen(4901) and is provided with a self generated form (4902). The Definition(4902) is formed of the Name cell, where the name of the issue can betyped in, and a Category drop-down menu (4903) that offers the followingoptions: Plant, Process, Process Stream, Sampling Point, and Issue. InFIG. 49, the Authorized User selected Issue. As a result of thisselection the logic guiding the system disclosed here generates IssueType (4904). Clicking on the Issue Type drop-down menu (4905) willdisplay any issue type that will have been defined under the Add IssueModule. In this example the user would have the choice among three issuetype as displayed in FIG. 47.

Once the Authorized User selected pH Alert as the notification issuetype, the logic guiding the system disclosed here generates the Triggertable (4908), which displays all parameters tracked under the pH Alert.When the Trigger table (4908) is first generated, columns Low and Highare blank.

If the Authorized User had selected process instead of issue, thegenerated table would have asked the Authorized User to select aspecific process then would have generated a table with parametersmonitored for that specific parameter.

The Users section (4907) lists the users that have access to the Logand/or Report Component for the selected plant, which in this example isPlant #3. The approved users (4907) are presented, so that the user mayspecifically direct the notification. The checkbox next to the name,Judy Black, has been selected, indicating that she is the user that willreceive this notification.

At this point, the Authorized User can complete the Trigger table(4908), and define the high and/or low triggers for the specificparameters. In FIG. 49, the user has identified 12 alerts per day as atrigger. In this scenario, Judy Black will receive a notification anytime the pH Alarm value exceeds 12 alerts per day. Additional commentsare entered in the Description text field (4906). The Submit button(4909) is selected when input is complete and the information addedbecomes part of the data store for the system.

FIG. 50 illustrates the Notification List screen, which enables the useroption to review, edit or delete existing notifications for the selectedfacility within a specified organization. This module is accessed byclicking on the Notification List button on the left side of the page(5001). The Plant Notifications table (5002) lists the notificationcurrently documented for Plant #3. The new plant notification, pH Alert(5003) has been added to the Notification List. Selecting Edit button(5004) launches Edit Notifications screen as displayed in FIG. 51. EditNotifications (5101) allows the user to update Notification Definition(5102) and Description (5103) when required. In this example, Sam Jones(5104) was added as a recipient of the pH Alert notification. The Highand Low triggers for the specific parameters in the Trigger table (5105)can be modified as well. The latest changes are logged and displayed inLast Edit Track (5106), identifying the name of editor and the date lastmodified. Changes are saved upon selecting Submit button (5107).

FIG. 52 illustrates the Add Task screen, will allows the Authorized Userto define a new task that will be added to the list of plant tasks for aselected facility within a specified organization. Under the logicassociated with the system disclosed here tasks are sub units of theaction module. Hence an action will be formed by a defined set of tasks.To access this module the user clicks on the Add Task button on the leftside of the screen (5201) and is provided with a self generated form(5202). To define a new task, the Authorized User will enter a name inthe Title field (5202); in this example the task is Verify flow meter. ADescription text field (5203) is available to provide additionalinformation on the task. A contact name can be provided for the task(5204); in this case, the contact name is Jim Smith. If applicable, anydocuments can be uploaded by clicking Upload file button (5205) andlinks can be attached by clicking Attach Link button (5206). The Submitbutton (5207) is selected when input is complete.

FIG. 53 illustrates the Tasks List screen, which enables the AuthorizedUser option to review, edit or delete existing facility tasks for theselected facility within a specified organization. This module isaccessed by clicking on the Task List button on the left side of thepage (5301). The Task List table (5302) lists the tasks currentlyentered for Plant #3. Based on the example above, Verify flow meter andJim Smith, have been added to the Task List (5303). Selecting Editbutton (5304) under the Verify Flow Meter Task opens the Edit Taskscreen displayed by FIG. 54. The Edit Task screen is where theAuthorized User is permitted to update Task Requirements (5402),Description (5403), and Contact Name (5404) as necessary. Any documentscan be uploaded by clicking Upload file button (5405) and links can beattached by clicking Attach File button (5406). The latest changes arethen logged in the database and are displayed in Last Edit Track (5407),which identifies the name of editor and the date last modified prior tothe present change. Selecting Submit button (5408) saves the changesthat were just completed.

FIG. 55 illustrates the screen display for Add Action, where theAuthorized User defines a new action for the selected facility within aspecified organization. An action is a combination of tasks which needto be performed in a given order. These tasks can be global tasks orfacility-specific tasks. To access this module the user clicks on theAdd Action button on the left side of the screen (5501) and is providedwith a self generated form (5502). In FIG. 55, the Definition table(5502) lists the new action titled pH adjustment. The trigger for anaction message to be issued is defined by using the Event Type drop-downmenu (5503). The options under the Event Type drop-down menu include logdata, sent notification, published report and published chart. Under theexample, the new action is triggered by a notification. In that case,the logic used for the system disclosed here generates the list ofnotifications (5504) available in the system. This list presented inFIG. 55 is an example of a table generated by the List Action Modulewhich is auto populated by the system's display element . . . .

Additional comments may be entered in the Description text field (5505).A Tasks table (5504) generated by the system disclosed here logic listsall Global and Facility Tasks currently assigned for Plant #3. The usermust select the tasks associated with the action but also to rank thesequence in which these tasks need to take place. In this example, EPAreport is the Global Task, denoted by the Task Type, which isorganization. This task is the first one to be performed, as it is notedas being Step 1. Verify flow meter is a facility Plant #3 task, denotedby the Task Type, which is plant. This task is to be achieved once theEPA report has been taken into consideration, as noted by Step 2.

The system disclosed here also generates the list of authorized Plant #3System Users (5507), from which the Authorized User selects therecipient or recipients of the action notice, that will be generatedonce the trigger will have been activated. The trigger in this exampleis when the number of daily pH alerts will exceed 12. Under FIG. 49,Judy Black was selected as the contact; in FIG. 55 Jim Smith wasselected as the user to be the contact for this action. The Submitbutton (5508) is selected when input is complete.

FIG. 56 illustrates the Action List screen, which enables the useroption to review, edit or delete existing facility actions within aspecified organization. This module is accessed by clicking on theAction List button on the left side of the page (5601). The PlantActions table (5602) lists the actions currently assigned for Plant #3facility. In this example, pH adjustment (5603) has been added to thePlant Actions. Selecting Edit button (5604) launches the Edit Actionscreen displayed in FIG. 57, which enables the Authorized User to editthe information displayed for this specific action. The user ispermitted to update Action Name and Event Type (5702), Description(5704), the Step Order (5705) and User Name(s) (5706) as necessary. Thelist of notifications (5703) available in the system is triggered by theaction selected. In this example, the action is unchanged, but the usershave been changed from Jim Smith to Sam Jones. The latest changes arelogged and displayed in the Last Edit Track, identifying the name ofeditor and the date last modified (5707). Changes are saved uponselecting Submit button (5708).

5—Data Logging Component

The Log Data Component is the process of data input. There are fivefunctions in the Log Data Component that are only accessible forAuthorized Users within a specified organization. Each function iscomprised of a minimum of 3 modules and is presented in the followingfigures of the Log Data Component. Plant Log Manager Function Modulesare Plant Log Adding (FIG. 59), Plant Log Search (FIG. 60), and PlantLog Editing (FIG. 61). Process Log Manager Function Modules are ProcessLog Adding (FIG. 62), Process Log Search and Listing (FIG. 63), andProcess Log Editing (FIG. 64). Process Stream Log Manager FunctionModules are Process Stream Log Adding (FIG. 65), Process Stream LogSearch (FIG. 66), and Process Stream Log Editing (FIG. 67). SamplingPoint Log Manager Function Modules are Sampling Point Log Adding (FIG.68), Sampling Point Log Search and Listing (FIG. 69), and Sampling PointLog Editing (FIG. 70). Plant Issue Type Manager Function Modules arePlant Issue Log Adding Module (FIG. 71), Plant Issue Log Search andListing Module (FIG. 72), and Plant Issue Log Editing (FIG. 73). Byclicking on the component, a menu will appear with the linked modules,which are then each accessed by clicking on the individual modulebutton. Utilizing the form-driven user configurable computer implementedsystem, Authorized Users are able to log and store pertinent data foranalysis and reporting. The Log Data Component can be used to capturespecific operative data to retain data integrity and facilityefficiency. Plant #3 will be used as the sample plant to illustrate thefigures for the Log Data Component.

The plant definition module is comprised of, but not limited to, a plantlog listing module and plant log module (add/edit), a process loglisting module and process log module (add/edit), a process stream loglisting module and process stream log module (add/edit), and a samplingpoint log listing module and sampling point log module (add/edit) underthe system disclosed here.

The process begins with selecting the plant the Authorized User wants toaccess. FIG. 58 displays the Plant Listing screen (5801) that enablesthe user to view facilities currently maintained in the application. ThePlant Listing and Selection table (5802) is a list of the plants andtheir assigned contacts. Clicking Select button (5803) allows the userto review a plant's administrative and functional information and to logthe plant's data. A map (5804) provides the geographic location of allfacilities, which is auto populated by the system's display element.

FIG. 59 illustrates the screen display for Add Plant Log, where the userselects from the log Date and Time fields and drop-downs (5902). Toaccess this module the user clicks on the Add Plant Log button on theleft side of the screen (5901) and is provided with a self generatedform (5902). Additional information can be entered into the Descriptiontext field (5903), if user chooses to do so. Predefined plant-specificparameters are displayed, for which the Authorized User can input values(5904), as selected in FIG. 31. The plant log parameters listing moduleis activated to display the monitoring parameters in the operation ofthe plant. For those parameters that have been marked for use of specialoperands, the user can additionally choose whether the measurement isequal to, less than or greater than a particular value. In this example,Aug. 1, 2010 and 8:00 am are utilized for date and time, the value inputfor energy usage parameter=102, and “Normal’ is typed in the Descriptiontext field. The Submit button (5905) is selected when input is complete.

FIG. 60 displays the Plant Log Listing module, which enables the useroption to search and review existing plant logs by Date (6002) and/or byKey Word (6003). This module is accessed by clicking on the Search PlantLog button on the left side of the page (6001). Click Search button(6004), to generate the Search Results table (6005) containing log entryresults for all plant log input for the date range selected for Plant#3, organized by name and particular details. Selecting Edit button(6006) launches the Edit Plant Log screen (6101), which is part of thePlant Definition module of the form-driven user configurable computerimplemented solution. The screenshot displayed in FIG. 61, where theuser is permitted to make edits in the Plant Log. The page outlines theoriginal log displaying Date and Time (6102) of the original input, theComment field (6103), and the Logged Data table (6104). In this example,a measurement of the parameter, Energy usage has been changed from 102to 1020 (6105). The latest changes are logged and displayed in the LastEdit Track (6106) that displays the name of editor and the date lastmodified. Changes are saved when Submit button (6107) is selected.

FIG. 62 displays the Add Process Log screen, where the user inputs databy selecting from the log Date and Time fields and drop-down menus(6202). To access this module the user clicks on the Add Process Logbutton on the left side of the screen (6201) and is provided with a selfgenerated form (6202). Additional input fields are for process name,mode and stage. The user has the option of Master mode or Process mode.If Master mode is selected the information can be collected for allprocesses and process stages for the plant. If process mode is selectedthe information can be collected for only one process and stage for theplant. The user can select one or several processes for which data willbe logged in the Select Process drop-down menu (6203). In this example,the user selected Filter (6204), which was the process that was addedunder the add process module example. The Comment field (6205) may beutilized for descriptive information.

A predefined Process Parameter table (6206) is generated by the systemdisclosed here's display element, as well as the predefined ParameterLog (6207) and Chemical Log (6208) tables. The process log parameterlisting module and process log chemical listing module are activated todisplay the monitoring parameters and utilized chemicals in theoperation of the process. The Authorized User can to inputs value(s)into these tables. For those parameters that have been marked for use ofspecial operands, the Authorized User can additionally choose whetherthe measurement is equal to or less than/greater than a particularvalue. In this example, Aug. 1, 2010 and 8:00 am (6202) are utilized fordate and time, the process is Filter (6204), the log input values are332 for Pressure for Process Value, 20 for Temperature and 120 forAlkalinity, and no input for the Chlorine under Chemical Log. The Submitbutton (6209) is selected when input is complete.

FIG. 63 displays the Process Log Listing module, which enables the useroption to search and review existing process logs by a date range in theProcess Log Date Search table (6302), a process (6303) using thedrop-down Select Process menu (6304) and/or by key word in the Key wordSearch in comment section (6305). This module is accessed by clicking onthe Search Process Log button on the left side of the page (6301). WhenSearch button (6306) is clicked, the Process Value Log table (6307) isgenerated containing process log entry results for the requested query,which includes any predefined process parameters organized by name andparticular details. Selecting Edit button (6308) for a specific data logwill launches the Edit Process screen with all the informationpertaining to that data log. FIG. 64 displays the Edit Process screen(6401), which is part of the Plant Definition module of the form-drivenuser configurable computer implemented solution, permits the user tomake edits in the Process Log. The page outlines the original logdisplaying Date and Time (6402) of the original input, the Process table(6403), the Comment field (6404), the logged data in the Process ValueLog (6405), additional predefined assigned parameters in the ParameterLog (6406) and chemicals in the Chemical Log (6407). In this example,the value for Pressure was changed from 332 to 35 (6408), while allother information remained the same. The latest changes are logged anddisplayed in the Last Edit Track (6409), which identifies the name ofeditor and the date last modified. Selecting Submit button (6410) saveschanged.

FIG. 65 displays the Add Process Steam screen, where the user has theaccessibility to input data by use of log Date and Time fields anddrop-downs (6502), and to select Master or Process mode. To access thismodule the user clicks on the Add Process Stream Log button on the leftside of the screen (6501) and is provided with a self generated form(6502). With the Select Process Stream drop-down menu (6503), the userhas the option to choose one or all available process streams. In thePlant #3 example, the user would have three choices Product Water, RawWater, Filter feed (as illustrated in FIG. 41). In FIG. 65, the userselected Product Water. The Description field (6504) may be utilized foradditional information.

Once the process stream has been selected, the configurable computerimplemented system's display element generates three sets of tables, thepredefined Process Stream Parameters (6505), the system-predefinedParameter Log (6506) and the Chemical Log table (6507). The processstream log parameter listing module and process stream log chemicallisting module are activated to display the monitoring parameters andutilized chemicals in the operation of the process stream. Whengenerated, all three tables are blank and the Authorized User is able toadd the information as needed.

For those parameters that have been marked for use of special operands,the user can additionally choose whether the measurement is equal to,less than, or greater than a particular value. In this example, Aug. 1,2010 and 8:00 am are utilized for date and time, the process stream isProduct Water, the log input values are 332=Pressure for Process Value,120=TOC for Parameter, and no input for the Chlorine under Chemical Log.The Submit button (6508) is selected when input is complete.

FIG. 66 displays the Process Stream Log Listing module, which enablesthe user to search and review existing process stream logs by a daterange (6602), a process selected from the Process Stream drop-down menu(6603) and/or by Key Word (6604). This module is accessed by clicking onthe Search Process Stream Log button on the left side of the page(6601). Under the Process Stream drop-down menu (6603), the user canselect one or all process streams in the system. Under the Plant #3example the user would have three choices: Product Water, Raw Water,Filter feed (as explained in FIG. 41). The user selected Product Waterfor its query.

Once the user clicks on Search button (6605), the Process Stream Valuetable (6606) is generated of log entry results that display all processstream log input for the date range and process stream selected forPlant #3, and includes any predefined process parameters organized byname and particular details. Selecting Edit button (6607) for a specificdata point opens the Edit Process Stream Log window as displayed in FIG.67. The Edit Process Stream Log button (6701), which is part of thePlant Definition module of the form-driven user configurable computerimplemented solution, permits the user to make edits in the ProcessStream Log. The page displays the log displaying Date and Time (6702) ofthe original input, the Process Stream (6703), Comment field (6704), thelogged data in the Process Value Log (6705), additional predefinedassigned parameters in the Parameter Log (6706) and chemicals in theChemical Log (6707). In this example, the value for Pressure was changedfrom 332 to 250 (6708), and the TOC value was adjusted from 120 to 12(6709); there is no input for the Chlorine under Chemical Log. Thelatest changes are logged and displayed in the Last Edit Track (6710),identifying the name of editor and the date last modified. Changes aresaved upon selecting Submit button (6711).

FIG. 68 illustrates the Add Sampling Point Log screen, where theAuthorized User has the accessibility to input data by use of log Dateand Time fields and drop-downs (6802), and to select Master or Processmode. To access this module the user clicks on the Add Sampling PointLog button on the left side of the screen (6801) and is provided with aself generated form (6802). In the Select Sampling Point drop-down menu(6803), the Authorized User has the option to choose one or allavailable sampling points in the system. The Select Sampling Pointdrop-down menu will only display the sampling points that exist in thesystem. In the case of Plant#3, two sampling points are made available,Network and Lake Intake. The Comment field (6804) may be utilized foradditional information. In this example, the user selected Lake Intakeand as a result, the Parameter Log table (6805) is generated to enablethe Authorized User to upload the data. This data includes anypredefined sampling point parameters. The sampling point log parameterlisting module is activated and displays the monitoring parameters forthe sampling point. For those parameters that have been marked for useof special operands, the user can additionally choose whether themeasurement is equal to or less than/greater than a particular value. Inthis example, Aug. 1, 2010 and 8:00 am are utilized for Date and Time,the Sampling Point is Lake intake, the log input value is 12 forTurbidity in the Parameter Log table. The Submit button (6806) isselected when input is complete.

FIG. 69 illustrates the Sampling Point Listing module, which enables theAuthorized User option to search and review existing sampling point logsby date (6902), sampling point by drop-down menu (6903) and/or by keyword (6904). This module is accessed by clicking on the Search SamplingPoint Log button on the left side of the page (6901). The SelectSampling Point menu (6903) is a drop-down menu which enables the user tochoose one or all sampling points available in the system. In the caseof Plant #3, two sampling points are currently available, Network andLake Intake. Once the search criteria are set; the Authorized Userclicks on Search button (6905). The system disclosed here provides theAuthorized User with the Search Results. A table is generated ofsampling point log entry results (6906) that displays all log input forthe date range selected for Plant #3, with the predefined parametersorganized by name and particular details.

For additional detail on a specific point, selecting Edit button (6907)opens a new window, the Edit Sampling Point Log (7001) as displayed inFIG. 70. The Edit Sampling Point Log (7001), which is part of the PlantDefinition module of the form-driven user configurable computerimplemented solution, permits the user to make edits in the Process Log.The page outlines the original log displaying Date and Time (7002) ofthe original input, the Sampling Point (7003), the Comment field (7004),and the logged data in the Parameter Log (7005). In this example, thevalue for Turbidity was changed from 12 to 1.2 (7006). The latestchanges are logged and displaced in the Last Edit Track (7007),identifying the name of editor and the date last modified. Changes aresaved when Submit button (7008) is selected.

FIG. 71 illustrates the Add Issue Log screen, where the Authorized Userhas the accessibility to input issue log related data by selectingvalues from the Date and Time drop-down menus (7102). To access thismodule the user clicks on the Add Issue Log button on the left side ofthe screen (7101) and is provided with a self generated form (7102). TheAuthorized User has the ability to choose one issue type by using theSelect Issue Type drop-down menu (7103). In the case of Plant #3 threeissue types are currently logged in the system: pH alarm, FilterMaintenance and Software Maintenance (as illustrated in FIG. 47). TheComment field cell (7104) may be utilized for additional information. InFIG. 71, the Authorized User selected pH alarm as the issue type. Onceselected, the system disclosed here generates a blank log parametertable (7105) specific to the selected issue. The Authorized User assignsthe issue to another specific authorized user, which can be selectedfrom an Assign To drop-down menu (7106). Once complete the AuthorizedUser is done completing the form, the Authorized User click Submitbutton (7107). At that point, a notification will be sent to theassigned user, and it will be his/her responsibility to close the itemby acting on the issue and closing the issue through the issue logmodule on the system disclosed here. In the example in FIG. 71, theissue is being recorded on Aug. 1, 2010 at 8:00 am, the issue type is pHAlarm, the log input value is 6 pH alarms for that day and the assignedindividual is Judy Black.

FIG. 72 illustrates the Search/List Issue screen, which enables the useroption to search and review existing process logs by Date (7202), issuetype by the Select Issue Type drop-down menu (7203), assigned individualby using the Select contact name for the assigned issue drop-down menu(7204), Issue Status (open or closed) by drop-down menu (7205) and/or bykey word (7206). This module is accessed by clicking on the Search IssueLog button on the left side of the page (7201).

Once all the information is complete on the requested query, theAuthorized User clicks Search button (7207), and the system disclosedhere generates the Process Value Log table (7208) that meets theparameters set in the query. Clicking Edit button (7209) opens the EditIssue Log (7301) in FIG. 73, where the user is permitted to make editsin the Issue Log. The screen displays the log displaying Date and Time(7302) of the original input, the issue type (7303), Comment field(7304), and the logged data in the Parameter Log (7305). In this examplethe parameter value was changed from 6 to 20 (7308). The Assign to(7306) and Issue Status (7307) may be modified as well. The latestchanges are logged and displayed in the Last Edit Track (7309) andidentifies the name of editor and the date last modified. Changes aresaved when Submit button (7310) is selected.

6—Data Reporting Component

The Report Component provides the process for creating custom designreports, charts, models, and forms. There are four functions under PlantSelection for creating reports for single facilities and two functionsunder the Cross Facility for multiple facility that are only accessiblefor Authorized Users within a specified organization. The functions arecomprised of, but not limited, to 3 modules and are presented in thefollowing figures. Plant Report Manager Function Modules are ReportAdding (FIG. 75), Report Listing (FIG. 76), and Report Publishing (FIG.78). Plant Chart Manager Function Modules include Chart Adding (FIG.79), Chart Listing (FIG. 80), and Chart Publishing (FIG. 82). PlantSpecific Model Manager Function Modules are Model Adding (FIG. 83),Model Listing (FIG. 84), and Model Publishing (FIG. 86). Plant SpecificForm Manager Function Modules are Form Adding (FIG. 87), Form Listing(FIG. 88), and Form Publishing (FIG. 90). Reports across severalfacilities can also be created. The function and modules under CrossFacility are as follows. Global Report Manager Function Modules areReport Adding (FIG. 91), Report Listing (FIG. 92), and Report Publishing(FIG. 94). Global Chart Manager Function Modules are Chart Adding (FIG.95), Chart Listing (FIG. 96), and Chart Publishing (FIG. 98). Byclicking on the component, a menu will appear with the linked modules,which are then each accessed by clicking on the individual modulebutton. Utilizing the system disclosed here, Authorized Users are ableto present facility data in selected design modes. The Report Componentcan be used to compile data and create detailed analysis for a specificfacility or multiple facilities. Plant #3 will be uses as a sample plantin the following figures to illustrate the Report Component. See FIG. 16for instructions on how to add Plant #3 to the system.

The plant definition module is comprised of, but limited to, a reportlisting module and report definition module (add/edit), and a chartlisting module and chart definition module (add/edit) under the systemdisclosed here.

The process begins with selecting the plant the Authorized User wants toaccess. FIG. 74 illustrates the Plant Listing screen (7401) in theReport Component. The Plant Listing screen allows the Authorized User toselect an individual facility or all facilities currently maintained inthe application to be used in a report or chart. The Plant Listing andSelection table (7402) is a directory of the plants and their assignedcontacts. A map (7405) provides the geographic location of allfacilities, which is auto populated by the system's display element. Inthe case of the single plant reporting and charting capabilities, underthe following components in the Report Component, Plant #3 is theexample facility. Clicking Select button (7403) allows the user toaccess the chart and report functionalities on parameters for onefacility (Plant#3). To access the chart and report if clicking on selectall plants (7404), the user will access the chart and reportfunctionalities focusing on all global parameters

FIG. 75 displays the Add Report screen, where the Authorized User hasthe ability to generate a new report utilizing logged data stored in thedatabase of the system disclosed here. To access this module the userclicks on the Add Report on the left side of the screen (7501) and isprovided with a self generated form (7502). A Report Name (7502) istyped in the Name field. A description field can be utilized foradditional detail. The date and time range (7503) of the logged data tobe extracted is selected for the report. When the Add Report window isfirst opened, Category (7504) is the only line visible in the ReportFocus table. At that point, the Authorized User clicks on the Categorydrop-down menu (7505) and selects from one of the available data logoptions: Plant, Process, Process Stream, Issue and Sampling Point. Thisdrop down menu activates the access to the report processes listingmodule, the report process streams listing modules, the report samplingpoint listing module, the report parameters listing module and thereport chemicals listing module which are all part of the reportdefinition module. In FIG. 75, the Authorized User selected Process Logand the Process Value checkboxes (7506) are displayed, The System (7507)and Type (7508) drop-down menus (7509, 7510) are also displayed. A subtype may be selected as well, if applicable. The value of Filter wasselected from the System drop-down menu. The Authorized User will selecteither a Parameter or Chemical from the Type drop-down menu. In theexample presented in FIG. 75, the user chooses Parameter, which promptsthe system disclosed here to generate the Parameter checkboxes (7511),and the Submit Report to checkbox (7512). The checkboxes will list thepredefined data linked to the option selected.

The Authorized User selects the desired checkboxes for Process Values,Parameters and the Report Recipients. The Submit button (7513) isselected when input is complete.

FIG. 76 displays the Report List screen, which enables the user optionto review and edit, run or delete existing reports. This page isaccessed by clicking on the Report List button on the left of the page(7601). The List of Existing Reports (7602) lists the reports currentlygenerated in the system by name and particular details. Filter Report(7603) has been added to the List of Existing Reports (see FIG. 75).Selecting Edit button launches an Edit Report screen. Selecting Runbutton (7604) for Filter Report will launch the Report Generating screen(FIG. 77), which is also the report rendering module part of theform-driven user configurable computer implemented solution.

The Report Generating screen (7701) is where the Authorized User willproduce a report based on the previous selections. The selected reportis displayed by Report Name (7702). The format is selected by the SelectFormat drop-down menu (7703), which provides three reporting layouts:HTML, Comma Delimited and Table Format. In FIG. 77, the Authorized Userchooses the Table Format. Specific statistical analysis can be added tothe report output by clicking the Statistical Analysis checkboxes. Inthe example in FIG. 77, the Filter Report will be generated in a tableformat and the system disclosed here will also provide specificstatistical analysis by clicking the Statistical Analysis checkboxes(7704). In this example, the average for both pressure and temperatureis selected. Both parameters were selected under FIG. 75. The Submitbutton (7705) is selected when input is complete. The output ispresented in table format in the Publish Report screen (7801), where thereport is presented in the table format (7802). The Authorized User hasthe option to export the report to Excel (7803) or to file and e-mail(7804) to the identified user in FIG. 75.

FIG. 79 illustrates the screen display for Add Chart, where theAuthorized User has the ability to generate a new chart utilizing loggeddata stored in the database of the system disclosed here. To access thismodule the user clicks on the Add Chart button on the left side of thescreen (7901) and is provided with a self generated form (7902). A chartname (7902) is typed in the name field and date/time range (7903) of thelog data to be extracted is selected for the chart. A description fieldcan be utilized for additional detail. When the Add Chart window isgenerated, the Category (7904) is the only line visible in the ChartFocus table. At that point, the Authorized User clicks on the Categorydrop-down menu (7905), and selects from one of the following Plant,Process, Process Stream, Issue and Sampling Point. This drop down menuactivates the access to the chart processes listing module, the chartprocess streams listing modules, the chart sampling point listingmodule, the chart parameters listing module and the chart chemicalslisting module which are all part of the chart definition module. InFIG. 79, the user selected Process Log and the Process Value checkboxes(7906) are displayed. The System (7907) and Type (7908) drop-down menus(7909, 7910) are also displayed. A sub type may be selected as well, ifapplicable. In the example, the user chooses Filter, and has the choiceof Parameters and Chemicals; the user chooses Parameter which promptsthe system disclosed here to generate the Parameter checkboxes (7911)and the Submit Report to checkbox (7912). The checkboxes will list thepredefined data linked to the option selected.

The Authorized User selects the desired checkboxes for Process Values,Parameters and the Report Recipients. The Submit button (7913) isselected when input is complete.

FIG. 80 illustrates the screen display for Chart List, which enables theuser option to review and edit, run or delete existing charts. Thismodule is accessed by clicking on the Chart List button on the left ofthe page (8001). The table (8002) lists the charts currently produced byname and particular details. Based on the example above, Filter Profile(8003) has been added to the List of Existing Charts. Selecting Editbutton launches an Edit Report screen. Selecting Run button (8004) willactivate the chart rendering module part of the formdriven userconfigurable computer implemented solution for Filter Chart, and displaythe window depicted by FIG. 81.

FIG. 81 illustrates the screen display for Chart Generating (8101),where the user is able to produce a chart based on preceding selections.The selected chart is displayed by Chart Name (8102). The user selectsone of two formats using drop-down menu (8103), Time-based andNon-time-based. In FIG. 81, the user has chosen a time-based chart. Atthat point the system disclosed here self generates all the remaininglines displayed in FIG. 81. The parameters listed are the X-axis (8104),Y-axis (8105), chart type (8106), and chart title (8107), all of whichprovide drop-down menus to build the graph. In the example above, theFilter Pressure Profile chart for July 2010 will be charted on atime-based format with Log-Date and Time on the X axis, Filter Pressureon the Y Axis, in a line chart type. Draw button (8108) is selected wheninput is complete. FIG. 82 illustrates the screen display for PublishChart (8201), where the chart is presented in the format (8202) asselected. The user clicks Send and Archive button (8203) to file indirectory.

FIG. 83 illustrates the screen display for Add Model, where the user hasthe ability to add to the facility's data library a model utilizinglogged data. A model is considered as a tailored report for whichpredefined parameters are identified by the authorized user. To accessthis module the user clicks on the Add Model button on the left side ofthe screen (8301) and is provided with a self generated form (8302). Amodel name (8302) is typed in an active cell. The category drop-down(8303) defines the module that will be modeled. The drop-down menu(8303) provides five choices plant, process, process stream, samplingpoint and issue. Once the Authorized User selects the category, thecomputer-implemented approach will generate a second drop-down menu(8304), enabling the user to select the model implementation focus. Inthe example set forth in FIG. 83, the Authorized User selected processand under the second drop-down selected Filter. In the case of Plant#3,the other option would have been Tank (FIG. 38). Once the AuthorizedUser has selected Filter, the system disclosed here generates a seriesof lists that will enable to define the data feeds to the model. Amongthese categories are the listed Parameters (8305) from which the userselects the key parameters which would apply to the model. For eachparameter selected, the system disclosed here will request the user tobetter qualify the data to be used through a series of options use rawdata, use hourly average, use daily average. A second list is chemicalusage (8306). For each chemical used at the facility the Authorized Userhas the option to select the chemical and use dose or chemical type asan input to the model. If the model is more complex, the user will clickthe complex model option checkbox (8307), which will prompt the user formore explanation on the model.

Then the user is prompted to define the model output as either a reportor a chart (8308). The user is also prompted in defining the Users ofthe model (8309).

The model can either be uploaded as a file or as a link (8310). Ineither case the model format will have to have been pre-approved by theAuthorized User to be certain the format is compatible with the formatof the system disclosed here. Once all the data is in place, theAuthorized User can submit the information by clicking on Submit button(8311), which will link the model to the application and preset the datainput when in use.

FIG. 84 illustrates the Model List screen, for which enables theAuthorized User to review and edit or delete existing models. This pageis accessed by clicking on the Model List button on the left of the page(8401). The List of Available Models table (8402) lists the modelscurrently produced by name and particular details. Filter efficiencymodel (8403), which was added in FIG. 83, has been added to the List ofAvailable Models. By selecting Edit button (8404) on the filterefficiency model, the system disclosed here will open the Add New modelwindow with the filter efficiency model information already populated(see FIG. 83). Clicking Run button (8405) on will open the Run Modelscreen for the selected facility, as displayed in FIG. 85.

The Model Run screen (8501) enables the user option to define the timeperiod and format output for a specific model run at a given facility.The name of the selected model is displayed in the Modal Name (8502). Inthe Time Selection drop-down menus (8503), the Authorized User sets thetime frame over which the model will be run. Since the model output wasdefine as a report (see FIG. 83), the system disclosed here displays theSelect Format drop-down menu (8504).

The Authorized User can define the format of the report through thedrop-down menu (8504), which provides three reporting layouts: HTML,Comma Delimited and Table Format. In FIG. 85, the Authorized Userchooses the Table Format. Specific statistical analysis can be added tothe report output by clicking the Statistical Analysis checkboxes(8505). To summarized, the Filter Efficiency Model Report will begenerated in a table format; the system disclosed here will also providethe average for both pressure and flow, which were the parametersselected as input to the model (see FIG. 83). The Submit button (8506)is selected when input is complete. FIG. 86 illustrates the screendisplay for the output Model Publishing Module (8601), where the outputis presented in the table format (8602). The results of the model arepresented in Removal—EFF column (8603). The user can click Export to MSExcel button (8604) or Send and Archive button (8605) to e-mail to theuser identified user in FIG. 83 (See User (8306)).

FIG. 87 displays the Add Form screen, where the Authorized User has theability to add to a form facility's data library by utilizing loggeddata. A form is considered as a tailored report for which predefinedparameters are identified by the Authorized User. To access this modulethe user clicks on the Add Form button on the left side of the screen(8701) and is provided with a self generated form (8702). A form name istyped in the Name cell. The Category drop-down menu (8703) provides fivechoices: Plant, Process, Process Stream, Sampling Point and Issue. Oncethe Authorized User selects the category, the system disclosed heredisplays the System drop-down menu (8704), enabling the user to selectthe model. In FIG. 87, the Authorized User selected Process Stream andselected Product Water from the System drop-down menu. In the case ofPlant#3, the two other options would have been Filter feed and Raw water(See FIG. 41).

Once the Authorized User has selected Product Water, the systemdisclosed here generates Data Input (8705), which is a list ofparameters that enables the user to define the data required by theform. For each parameter selected, the system disclosed here willrequest the user to better qualify the data by selecting from variousoptions, such as minimum, maximum, daily average, or monthly average.The Authorized User is then prompted to define the form output, whichwould be either a report or a chart (8706). If the form is more complex,the user will click the Complex Model Option (8707), which will promptthe user for more explanation on the form. The Authorized User is alsoprompted to define the users of the form by selecting a User andapproval option (8708).

The form can either be uploaded as a file or as a link by clickingeither Upload File or Attach Link (8709). In either case the form formatwill have to have been pre-approved by the Authorized User to be certainthe format is compatible with the format of the system disclosed here.Once all the data is in place, the Authorized User can submit theinformation by clicking on the Submit button (8710), which will link themodel to the application and preset the data input when in use.

FIG. 88 displays the Form List screen (8801), which enables the user toreview and edit or delete existing forms. This page is accessed byclicking on the Form List button on the left of the page (8801). TheList of Existing Forms table (8802) lists the forms currently producedby name and particular details. Permit 101 (8803), which was added FIG.87, has now been added to the List of Available Forms. Selecting Edit(8804) on the Permit 101 will open the Add New Form window with thePermit 101 information already populated (See FIG. 87). When Run (8805)is selected on the Permit 101, the system disclosed here will open theRun Form window for the selected facility as displayed in FIG. 89.

Run Form (8901) enables the Authorized User to define the time periodand format output for a specific form output at a given facility. Thename of the selected form is displayed in Report Name (8902). TheAuthorized User sets the time frame over which the form will be run inTime Selection (8903). The Authorized User then specifies if a raw datareport should be generated or not. In the case the Authorized User doesrequest a raw data report (8904) and the system disclosed here generatesthe Select Format drop-down menu (8905) and Statistical Analysis options(8906).

The Select Format drop-down menu (8905) provides three reporting layoutoptions for the raw data HTML, Comma Delimited and Table Format. In FIG.89, the user chooses the Table Format. Statistical analysis can be addedto the report output by selecting from the Statistical Analysischeckboxes (8906). In FIG. 89, Raw Data Report will be generated in atable format and the system disclosed here will also provide the averagefor Flow, Temperature and TOC data, which were the parameters selectedas input to the form (see FIG. 87). The Submit button (8907) is selectedwhen input is complete.

FIG. 90 displays the Form Publishing screen (9001), where the output ispresented in a print preview layout (9002). The Authorized User canclick Export to MS Excel button (9003) or Send and Archive button tosend the form to a user that was previously defined (see FIG. 87). Last,the user can open the raw data report by clicking on button (9005).

To create a global report across several facilities, the Authorized Userwould use the Add Global Report, displayed in FIG. 91. To access thismodule the user clicks on the Add Global Report button on the left sideof the screen (9101) and is provided with a self generated form (9102).A report name is typed in the Name field (9102) and date/time range ofthe data to be extracted is selected in the Time Selection table (9103).When the Add Global Report window is first displayed, only the Categorydrop-down menu (9104) is visible. The Authorized User can select one ofthe following: Plant, Process, Process Stream, Issue and Sampling Point.In FIG. 91, the user selected Plant Log. Once selected, the computerimplementation approach generates the Type drop-down menu (9105), whichoffers the choice between parameters and chemicals. In FIG. 91, the userchooses Parameter. If Parameter is selected, the system disclosed heregenerates Global Parameters (9106), which are global parameters andglobal parameters monitored at the plant level.

After selecting from the Parameter options, the Authorized Useridentifies specific recipients of the report from the Submit Report tocheckboxes (9107) if appropriate. The Submit button (9108) is selectedwhen input is complete.

FIG. 92 displays the Global Report List screen (9201), where theAuthorized User to review and edit, run or delete existing globalreports. This page is accessed by clicking on the Organization button onthe left of the page (9201). The List of Existing Global Reports (9202)lists the current reports by name and particular details. The SludgeProduction Report (9203) has been added to the List of Existing GlobalReports. Selecting Run button (9204) for Sludge Production Report willopen the Global Report Generating window depicted by FIG. 93, where theAuthorized User can produce a report based on the previous selections.The report selected is displayed in the Report Name field (9302). Theformat is selected in the Select Format drop-down menu (9303), whichprovides three layout options: HTML, Comma Delimited and Table Format.In FIG. 93, the user chooses the Table Format. Statistic analysis can beadded to the report output by selecting from the Statistical Analysisoptions (9304). In FIG. 93, the Sludge Production Report will begenerated in a table format; the system disclosed here will also providethe total amount of sludge produced by each facility over the definedtime period. The Submit button (9305) is selected when input iscomplete. Clicking Submit button will launch the Publish Global Reportscreen (9401), where the report is presented in the table format (9402)as selected. The user has the option to click Export to MS Excel button(9403) or Send and Archive button (9404) to the user identified in FIG.87.

FIG. 95 displays the Add Global Chart screen, where the Authorized Userhas the ability to generate a new global chart utilizing logged datastored in the database of the system disclosed here. To access thismodule the user clicks on the Add Global Chart button on the left sideof the screen (9501) and is provided with a self generated form (9502).A chart name is typed in the Name field (9502) and the date/time rangeof the data to be extracted is selected in the Time Selection table(9503). When the Add Global Report window is generated, only theCategory drop-down menu (9504) is visible. At that point, the AuthorizedUser clicks from the Category drop-down menu (9505) and selects from oneof the following: Plant, Process, Process Stream, Issue and SamplingPoint. In FIG. 95, the user selected Plant Log. Once selected, thecomputer implementation approach generates the Type drop-down menu(9506), which offers two choices of data types: Parameter or Chemicals.In FIG. 95, the user chooses Parameter using the drop-down menu (9507).When Parameter is selected, the system disclosed here generates theParameter checkboxes (9508) which list the global parameters monitoredat the plant level.

After the Authorized User identifies the Parameter that will be used inthe chart, he or she identifies specific recipients of the report bymaking a selection from the Submit Report to checkboxes (9509). TheSubmit button (9510) is selected when input is complete.

FIG. 96 displays the Global Chart List screen (9601), where the user canreview and edit, run or delete existing charts. The List of ExistingGlobal Charts (9602) lists the previously created charts by name andparticular details. Sludge Production (9603), which was added in FIG.95, has now been added to the List of Existing Global Charts. SelectingRun (9604) for Sludge Production, the system disclosed here will openthe Global Chart Generating window depicted in FIG. 97.

The Global Chart Generating screen (9701) is where the user can a chartbased on report generation. This page is accessed by clicking on theGlobal Chart List button on the left of the page (9601). The reportselected is displayed in the Report Name field (9702). The AuthorizedUser will choose one of two formats using the Select Format drop-downmenu (9704), either Time based or Non-time based. In FIG. 97, the userselects a time based chart. If Time based is selected, the systemdisclosed here generates the other chart properties, which include: theX-axis (9704), Y-axis (9705), chart type (9706), and chart title (9707).In this example, the Sludge Production Global Chart will be charted on atime based format with Log-Date and Time on the X axis, Filter Pressureon the Y Axis, in a line chart type. The Draw link (9708) is selectedwhen input is complete. Clicking Draw button launches the Publish GlobalReport (9801) in FIG. 98, which displays a print preview of the chart(9802). The user clicks Send and Archive button (9803) to file send thechart to the users identified under FIG. 87, at the same time the fileis archived in the database.

7—User Home Page Component

The Home Page Component presents an organizational tool for the user tomanage work production. There is one function under Plant Selection, twofunctions under the User site set-up and the General Information ManagerFunction that are only accessible for Authorized Users within aspecified organization. The functions are comprised of, but not limited,to 3 modules and are illustrated in the following figures. WorkflowManager Function Modules are Specific Plant Action Listing (FIG. 99),User Specific Notification Listing and Selecting (FIG. 100), Action Logand Task Description (FIG. 101). The functions and modules under TheUser Site Set-up are as follows: Dashboard Manager Function Modules areHome Page Set-up (FIG. 104), Data Selection (FIG. 105), Chart Selection(FIG. 106), and Pre-set File (FIG. 107). Personal Profile ManagerFunction modules are: User Profile Viewing and Editing (FIG. 108), andUser and Organization Permission Access (FIG. 109). The modules underGeneral Information Manager Function are: Bulletin Board Posting (FIG.110), Bulletin Board Response (FIG. 111), Announcement Listing andViewing (FIG. 112), and File Download and Link Access (FIG. 113). Byclicking on the Component, a menu will appear with the linked modules,which are then each accessed by clicking on the individual modulebutton. Utilizing the system disclosed here, Authorized Users are ableto design personalized reporting views, review personal access, andaccess organizational information. The Home Page Component enables theuser to customize reports/charts for view only status for analysis.

The process begins with selecting the plant the Authorized User wants toaccess. FIG. 99 illustrates the screen display for User Home Page PlantListing and Selection (9901) under the Home Page Component enabling theAuthorized User the option to review an individual facility currentlymaintained in the application. The table (9902) is a directory of theplants and three options for review: notifications, actions, and plantdetails for that particular plant. Clicking on Select button (9903) willallow the Authorized User to access the notifications for Plant #3,while clicking Select button (9904) will allow the Authorized User toaccess the actions for Plant #3. A map (9905) provides the geographiclocation of all facilities, which is auto populated by the system'sdisplay element.

Selecting notifications (9903) in FIG. 99, a window opens to FIG. 100.FIG. 100 illustrates the screen display for In-box Notification (10001),where the designated user receives notifications pertaining to aspecific plant, self generated by the system disclosed here oncespecific triggers were activated. Notifications triggers are set underthe Define Component of the system disclosed here. The notification list(10002) presented as an example contains the fundamental information andis sent when a defined issue has reached its target value. Once the userhas taken note of the notification, the user has the ability to removethe message from the list by checking the box left to the message andclick on Delete Checked Items button (10003). Based on the example abovein Add Notification (FIG. 49), pH Alert, a new notification, is sent forthe organizational review.

Selecting any action (9904) in FIG. 99 will open the window illustratedin FIG. 101. FIG. 101 illustrates the screen display for Action Logs(10101), where the designated user receives the actions required for afacility. The action list (10102) contains the fundamental informationand is sent when a defined issue has reached its target value, andsubsequently alerts the designated user(s). Click on Delete CheckedItems button (10103) to remove an action from the list. Based on theexample above in Add Action (FIG. 55), pH adjustment, a new action, issent for the organizational review. Selecting Detail button (10104),FIG. 102 illustrates the screen display for Action Details (10201),where the user is able to view action record information (10202),description (10203), and the task step order (10204). Note that theexamples are: 1) EPA report from FIG. 22, Add Global Task is step 1 and2) Verify Flow Meter from FIG. 52, Add Task for Individual Facility isstep 2. Selecting Detail button (10205) in FIG. 103 illustrates thescreen display for Task Description (10301), where the user is able toview the task record information (10302) and the detail (10303) whichdirects the task completion order. Step 1 requires a download of EPATask 101 which is executed by clicking on Browse button (10304) tolocate file and Download File button (10305) to execute.

FIG. 104 illustrates the screen display for Dashboard Manager whichenables the user to select settings to individualize their homepageview. The user clicks on the Dashboard Manager button on the left sideof the screen (10401) and is provided with a self generated form(10402). The fields in Format Selection (10402), Content Display (10403)and Customize Display (10404) utilize drop-down menus to alter theappearance of the homepage to suit the user's preference. Under Format(10402), the table size may be selected (10405). Under Content Display(10403), there are selections in facility listing (10406), ChartSelection (10407), Pre-set module (10408), and Data Selection (10409).Under Customize Display (10404), the Font Size (10410) and BackgroundColor (10411) can be modified. Click on View Display button (10412) topreview the page with selected settings. Clicking Submit button (10413)displays the screen in FIG. 105. FIG. 105 illustrates the screen displayfor Dashboard Manager (10501) for Home Page Data Selection (10502). Theuser utilizes the field to input the number of parameters (10503)required. The Select Parameter Table (10504) allows the user to utilizethe drop-down menus to choose the Plant Location, Category, System,Parameter, and two modes of Data Types for the data requested. Submitbutton (10505) is selected when input is completed for the nextscreenshot in FIG. 106. FIG. 106 illustrates the screen display forDashboard Manager (10601) for Home Page Chart Selection (10602). Theuser utilizes the drop-down menu in Select Location (10603) to choose afacility. In this example, Plant #3 is selected. The applicable chartsare presented in table format (10604) and the user selects the timeframe (10605) utilizing a drop-down menu. Click on the desired cellunder the Select column (10606) and a checkmark will designate the chartrequested. Click on Submit button (10605) to save changes. FIG. 107illustrates the screen display for Dashboard Manager (10701) for HomePage Pre-set Selection (10702). The user clicks on the radio box to AddPicture, File or Link (10703) and utilizes the drop-down menu in Source(10704) to make the selection. In this example, Link is selected. Clickon Upload (10705) to execute process. A Message Summary (10706) is theother option for the user to perform. Click Submit button (10707) tosave changes.

FIG. 108 illustrates the screen display for User Profile, where the useris given access to create a personal profile. The user clicks on theUser Profile button on the left side of the screen (10801) and isprovided with a self generated form (10802). Fundamental information(10802) is required and as well as a password (10803) to log on to theapplication. The Submit button (10804) is selected when input iscomplete. Also available on this page is the User Access Definitiontable (10805), which displays on a read only mode the authorizedcomponent functions the user has access to within the system disclosedhere. User Access is managed from the Administer Component. FIG. 109illustrates the screen display for User Access Permission (10901, wherethe authorized is able to review personal access to the components.

FIG. 110 illustrates the screen display for Bulletin Board, where theuser can view informational postings from users within the organization.The user clicks on the Bulletin Board button on the left side of thescreen (11001). The table lists the topics currently available fordiscussion (11002), and the full posting and related replies are viewedby selecting detail button (11003) on the topic row. To add a new topicfor posting, the user types in the New Topic field for Topic Selection(11004) and Message (11005). The Submit button (11006) is selected wheninput is complete. FIG. 111 illustrates the screen display for BulletinBoard Response (11101), which enables the user to review the selectedtopic (11102) and the associated responses (11103); click on Detailbutton (11104) to see full response. To post a new response, the userutilizes the field marked Post New Response (11005). Response is postedupon selecting Submit button (11106).

FIG. 112 illustrates the screen display for Files and Links List, wherethe approved users have access to review existing global files andlinks. The user clicks on the Files and Links button on the left side ofthe screen (11201). The file table (11202) lists the documents currentlyavailable and clicking Download button (11203) on the selected rowexecutes this process. The link table (11204) lists the sites availableand clicking on the address (11205) on the selected row executes thisprocess. The links and files visible under this module of the systemdisclosed here were added exclusively from the Administer Component,thus keeping task specific or plant specific documents distinct andrespecting possible confidentiality considerations placed on specificdocuments.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. However, variousmodifications and changes may be made thereto without departing from thebroader spirit and scope of the invention. The specification anddrawings are, accordingly, to be regarded in an illustrative senserather than a restrictive sense.

What is claimed is:
 1. A form-based user-configurable computer-implemented system for managing processing plant information, the system comprising: a plant definition module comprising a form displayed on a computer screen capable of allowing a user to enter and save information about said processing plant, said plant definition module further comprising: a processes listing module capable of displaying a list of processes in said plant; a sampling points listing module capable of displaying a list of sampling points in said plant; a sampling point logs listing module capable of displaying a list of sampling point log search fields for said plant; and a reports listing module capable of displaying a list of reports for said plant; a parameters listing module responsive to said plant definition module, capable of displaying a list of plant parameters; a parameter definition module responsive to said parameters listing module wherein said parameter definition module comprises a form displayed on said computer screen capable of allowing a user to enter and save information about at least one plant parameter; a process definition module responsive to said processes listing module wherein said process definition module comprises a form displayed on said computer screen capable of allowing a user to enter and save process definition information for said plant, said process definition module further comprising a process parameters listing module capable of displaying list of process parameters employed to monitor processes in said plant; a sampling points definition module responsive to said sampling points listing module wherein said sampling points definition module comprises a form displayed on said computer screen capable of allowing a user to enter and save sampling points definition information for said plant, said sampling points definition module further comprising a sampling point parameters listing module capable of displaying a list of sampling point parameters employed to collect information in the plant; and a report rendering module responsive to said reports listing module wherein said report rendering module comprises a form displayed on said computer screen further comprising a submit button, the actuation of which causes a report to be shown on said computer screen.
 2. The system of claim 1, wherein: said parameter definition module form further comprises: a plurality of parameter input fields responsive to user input comprising a name field, a units field, a minimum value field, and a maximum value field; a save button displayed on said computer screen that is responsive to user input; and capable of transferring the user-provided contents of said parameter definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into a computer memory; said process definition module form further comprises: a plurality of chemical definition input fields responsive to user input comprising a process name field and a process type field; a save button displayed on said computer screen that is responsive to user input; and a data movement element capable of transferring the user-provided contents of said organization definition input fields to a computer memory in response to a signal from said button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; and said sampling points definition module form further comprises: a plurality of sampling point definition input fields responsive to user input comprising a sampling point name field and a sampling point type field; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said sampling point definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory.
 3. The system of claim 2, further comprising a users listing module and a user definition module wherein said users definition module is responsive to said users listing module and said users listing module further comprises a user functions listing module and wherein: said users listing module is capable of showing a list of existing users of said system; said user definition module comprises a form displayed on said computer screen comprising a user definition input field; and said user functions listing module is capable of displaying and changing the modules accessible to a specific system user.
 4. The system of claim 3, further comprising: a sampling point log module responsive to said sampling point logs listing module, further comprising a sampling point log parameters listing module; and a report definition module responsive to said reports listing module, further comprising: a report sampling points listing module; and a report parameters listing module wherein: said sampling point log module comprises a form displayed on said computer screen showing at least one sampling point log field; said sampling point log parameters listing module is capable of displaying parameters employed to collect sampling point log information; said report definition module comprises a form displayed on said computer screen, said form comprising a report definition input field; said report sampling points listing module capable of displaying sampling points employed by the plant; and said report parameters listing module is capable of displaying parameters employed by the plant.
 5. The system of claim 4, wherein: said plant definition module further comprises a chemicals listing module; said system further comprises a chemical definition module responsive to said chemicals listing module; said process definition module further comprises a process chemicals listing module; and said a report definition module further comprises a report chemicals listing module; wherein: said chemicals listing module is capable of displaying chemicals employed in said plant; said chemical definition module further comprises a form displayed, on said computer screen, said form comprising a chemical definition input field; said process chemicals listing module is capable of displaying process chemicals employed in the plant; and said report chemicals listing module is capable of displaying chemicals employed in the plant.
 6. The system of claim 5, wherein: said plant definition module further comprises a process logs listing module; said system further comprises a process log module responsive to said process logs listing module, further comprising a process log parameters listing module and a process log chemicals listing module; and said report definition module further comprises a report processes listing module; wherein: said process logs listing module further comprises a form displayed on said computer screen, said form comprising a process log search field; said process log module further comprises a form displayed on said computer screen, said form comprising a process log field; said process log parameters listing module is capable of displaying parameters employed to collect process log information; said process log chemicals listing module is capable of displaying chemicals employed to collect process log information; and said report processes listing module is capable of displaying processes employed by the plant.
 7. The system of claim 6, wherein: said plant definition module further comprises a plant logs listing module; and said system further comprises a plant log module responsive to said plant logs listing module, further comprising a plant log parameters listing module; wherein: said plant logs listing module further comprises a form displayed on said computer screen, said form comprising a plant log search field; said plant log module further comprises a form displayed on said computer screen, said form comprising a plant log field; and said plant log parameters listing module is capable of displaying log parameters employed to collect plant log information.
 8. The system of claim 7, wherein: said plant definition module further comprises a process streams listing module and a process stream logs listing module; said system further comprises a process streams definition module responsive to said process streams listing module, further comprising a process stream parameters listing module and a process stream chemicals listing module; said system further comprises a process stream log module responsive to said process stream logs listing module, further comprising a process stream log parameters listing module and a process stream log chemicals listing module; and said report definition module further comprises a report process streams listing module; wherein: said process streams listing module is capable of displaying process streams employed by the plant; said process stream logs listing module comprises a form displayed on said computer screen further comprising a process stream log search field; said process streams definition module comprises a form displayed on said computer screen further comprising a process stream input field; said process stream parameters listing module is capable of displaying process stream parameters employed in the plant; said process stream chemicals listing module is capable of displaying process stream chemicals employed in the plant; said process stream log module comprises a form displayed on said computer screen further comprising a process stream log field; said process stream log parameters listing module is capable of displaying parameters employed to collect process stream log information; said process stream log chemicals listing module is capable of displaying chemicals employed to collect process stream log information; and said report process streams listing module is capable of displaying process streams employed by the plant.
 9. The system of claim 8, further comprising an organization definition module comprising a plants listing module and said users listing module wherein: said plant definition module is responsive to said plants listing module; said parameters listing module is responsive to said organization definition module; and wherein: said organization definition module further comprises a form displayed on said computer screen comprising an organization definition input field; and said plant definition module is capable of displaying a listing of plants controlled by said organization.
 10. The system of claim 9 wherein: said plant definition module further comprises a charts listing module; said system further comprises a chart definition module responsive to said charts listing module, further comprising: a chart processes listing module; a chart process streams listing module; a chart sampling points listing module; a chart parameters listing module; and a chart chemicals listing module; and said system further comprises a chart rendering module responsive to said charts listing module; wherein: said charts listing module comprises a display element capable of showing a list of existing charts for the plant; said chart definition module further comprises a form displayed on said computer screen comprising a chart definition input field; said chart process listing module is capable of displaying processes employed by the plant; said chart process streams listing module is capable of displaying process streams employed by the plant; said chart sampling points listing module is capable of displaying sampling points employed by the plant; said chart parameters listing module is capable of displaying parameters employed by the plant; said chart chemicals listing module is capable of displaying chemicals employed by the plant; and said chart rendering module comprises a form displayed on said computer screen comprising a chart rendering input field.
 11. The system of claim 10, wherein said system is implemented using a client-server architecture in which forms are displayed in a web browser on a client computer and data is stored on a server and wherein said client computer and said server communicate using an internet protocol.
 12. The system of claim 10 wherein: a) the organization definition module form further comprises; a plurality of organization definition input fields responsive to user input comprising: an organization name field; an organization description field; an organization contact person's name field; an organization address field; an organization phone number field; an organization fax number field; an organization email address field; an organization web address field; a plant quantity field; a user quantity field; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said organization definition input fields to a computer memory in response to a signal from said button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; b) the plants listing module further comprises a display element, said display element being capable of showing: a list of existing plants structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the plant definition module; and a create new plant button wherein said create new plant button is responsive to user input and wherein the actuation of said create new plant button causes the opening of the plant definition module with empty fields; c) said plant definition module form further comprises: a plurality of plant definition input fields responsive to user input comprising: a plant name field; a plant description field; a plant contact field; a plant address field; a plant phone field; a plant fax field; a plant email field; a plant web address field; a plant flow units field; a plant pressure units field; a plant temperature units field; a plant start date field; and a plant track history field; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said plant definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; d) the parameters listing module is further capable of displaying: a listing of parameters that are employed in the organization and shared across the plants of the organization when the parameters listing module is actuated from the organization definition module; and a listing of the parameters in the plant without the ability to share with other plants in the organization when the parameters listing module is actuated from the plant definition module; a list of existing parameters structured by name and description; at least one edit button for each existing parameter wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the parameter definition module; and an add new parameter button wherein said add new parameter button is responsive to user input wherein the actuation of said add new parameter button causes the opening of the parameter definition module with empty fields; e) said parameter definition module form input fields further comprise: a parameter description field; a parameter type field; and a parameter enforce minimum and maximum field; and a parameter special operands field; f) the chemicals listing module further comprises a display element, said display element being capable of showing: a list of existing chemicals structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the chemical definition module; and an add new chemical button wherein said add new chemical button is responsive to user input and wherein the actuation of said add new chemical button causes the opening of the chemical definition module with empty fields; g) said chemical definition module form further comprises: a plurality of chemical definition input fields responsive to user input comprising: a chemical name field; a chemical description field; a chemical type field; a chemical dosage units field; a chemical rate units field; a chemical loading units field; a chemical feed density units field; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; h) the processes listing module further comprises a display element, said display element being capable of showing: a list of existing processes structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the process definition module; and an add new process button wherein said add new process button is responsive to user input and wherein the actuation of said add new process button causes the opening of the process definition module with empty fields; i) said process definition module process definition input fields further comprise a process description field and a number of process stages field; j) the process parameters listing module further comprises a display element, said display element being capable of showing: a list of existing parameters structured by name comprising: a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter special operands field; and a check box for each parameter to accept or remove its usage for the process; at least one edit button for each existing parameter wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the parameter definition module; and an add new parameter button wherein said add new parameter button is responsive to user input wherein the actuation of said add new parameter button causes the opening of the parameter definition module with empty fields; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; k) said process chemicals listing module further comprises a display element, said display element being capable of showing: a list of existing chemicals structured by name comprising: a chemical name field; a chemical description field; a chemical type field; a chemical dosage units field; a chemical rate units field; a chemical loading units field; a chemical feed density units field; and a check box for each existing chemical to accept or remove its usage for the process; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the chemical definition module; and an add new chemical button wherein said add new chemical button is responsive to user input and wherein the actuation of said add new chemical button causes the opening of the chemical definition module with empty fields; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; l) said process streams listing module further comprises a display element, said display element being capable of showing: a list of existing process streams structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the process stream definition module; and an add new process stream button wherein said add new process stream button is responsive to user input and wherein the actuation of said add new process stream button causes the opening of the process stream definition module with empty fields; m) said process stream definition module form further comprises: a plurality of process stream definition input fields responsive to user input comprising: a process stream name field; a process stream description field; a process stream code field; a process stream type field; an upstream process field; a downstream process field; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said process stream definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; n) said process stream parameters listing module further comprises a display element, said display element being capable of showing: a list of existing parameters structured by name comprising: a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter special operands field; and a check box for each parameter to accept or remove its usage for the process; at least one edit button for each existing parameter wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the parameter definition module; and an add new parameter button wherein said add new parameter button is responsive to user input wherein the actuation of said add new parameter button causes the opening of the parameter definition module with empty fields; a save button displayed on said computer screen that is responsive to user input; and a data movement element capable of transferring the user-provided contents of said parameter definition fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; o) said process stream chemicals listing module further comprises a display element, said display element being capable of showing: a list of existing chemicals structured by name comprising: a chemical name field; a chemical description field; a chemical type field; a chemical dosage units field; a chemical rate units field; a chemical loading units field; a chemical feed density units field; and a check box for each existing chemical to accept or remove its usage for the process; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the chemical definition module; and an add new chemical button wherein said add new chemical button is responsive to user input and wherein the actuation of said add new chemical button causes the opening of the chemical definition module with empty fields; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; p) said sampling points listing module comprising a display element, said display element being capable of showing: a list of existing sampling points structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the sampling points definition module; and an add new sampling point button wherein said add new sampling point button is responsive to user input and wherein the actuation of said add new sampling point button causes the opening of the sampling point definition module with empty fields; q) said sampling points definition module input fields further comprise a sampling point description field and a a sampling point code field; r) said sampling point parameters listing module further comprises a display element, said display element being capable of showing: a list of existing parameters structured by name comprising: a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter special operands field; and a check box for each parameter to accept or remove its usage for the process; at least one edit button for each existing parameter wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the opening of the parameter definition module; and an add new parameter button wherein said add new parameter button is responsive to user input wherein the actuation of said add new parameter button causes the opening of the parameter definition module with empty fields; a save button displayed on said computer screen that is responsive to user input; and a data movement element capable of transferring the user-provided contents of said parameter definition fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; s) said plant logs listing module form further comprises: a plurality of plant log search fields, said fields being responsive to user input, and said plant log search fields comprising: a log date from search field; a log date to search field; a log description search field; a search button wherein said search button is responsive to user input; a list of existing plant logs retrieved based on said plan log search fields, and said list ordered by one from the group of said log date from, said log date to, and said log description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the plant log module; and an add new plant log button wherein said add new plant log button is responsive to user input and wherein of said add new plant log button causes the opening of the plant log module with empty fields; t) said plant log module form further comprises: a plurality of plant log fields responsive to user input comprising: a log date field; a log time field; a log description field; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said plant log input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; u) said plant log parameters listing module further comprises a display element, said display element being capable of showing: a list of existing plant parameters structured by name comprising; a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter special operands field; wherein the list of process parameters has been defined as part of said parameters listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said parameter definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; v) said process logs listing module comprises: a form displayed on said computer screen said form comprising: a plurality of process log search fields responsive to user input comprising: a log date from search field; a log date to search field; a process name selection search field; and a description search field; a search button displayed on said computer screen that is responsive to user input; a display element to display existing list of process logs retrieved based on user entered search fields and structured by log date, log time, process name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the process log module; and an add new process log button wherein said add new process log button is responsive to user input and wherein the actuation of said add new process log button causes the opening of the process log module with empty fields; w) said process log module form further comprises: a plurality of process log fields responsive to user input comprising: a log mode field; a log date field; a log time field; a log description field; a process name selection field; and a process stage field; a log mode selection choice button that allows the user to select a master mode to collect process log information for all processes and process stages for the plant in a single step; a log mode selection choice button that allows the user to select an individual mode to collect process log information for only one selected process and stage for the plant in a single step; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said process log input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; x) said process log parameters listing module further comprises a display element, said display element being capable of showing: a list of existing process parameters structured by name comprising; a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter measurement field; a parameter special operands field; wherein the list of process parameters has been defined as part of said parameters listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said parameter definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; y) said process log chemicals listing module further comprises a display element, said display element being capable of showing: a list of existing chemicals structured by name comprising: a chemical name field; a chemical description field; a chemical type field; a chemical dosage units field; a chemical dosage measurement field; a chemical rate units field; a chemical rate measurement field; a chemical loading units field; a chemical loading measurement field; a chemical feed density units field; a chemical feed density measurement field; wherein the list of chemicals has been defined as part of said chemicals listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; z) said process stream logs listing module form further comprises: a plurality of process stream log search fields responsive to user input comprising: a log date from search field; a log date to search field; a process stream name selection search field; and a description search field; a search button displayed on said computer screen that is responsive to user input; a display element to display existing list of process stream logs retrieved based on user entered search fields and structured by log date, log time, process stream name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the process stream log module; and an add new process stream log button wherein said add new process stream log button is responsive to user input and wherein the actuation of said add new process stream log button causes the opening of the process stream log module with empty fields; aa) said process stream log module form comprises: a plurality of process stream log fields responsive to user input comprising: a log mode field; a log date field; a log time field; a log description field; and a process stream name selection field; a log mode selection choice button that allows the user to select a master mode to collect process stream log information for all processes and process stages for the plant in a single step; a log mode selection choice button that allows the user to select an individual mode to collect process stream log information for only one selected process and stage for the plant in a single step; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said process stream log fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ab) said process stream log parameters listing module further comprises a display element, said display element being capable of showing: a list of existing process parameters structured by name comprising; a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter measurement field; a parameter special operands field; wherein the list of process parameters has been defined as part of said parameters listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said parameter definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ac) said process stream log chemicals listing module further comprises a display element, said display element being capable of showing: a list of existing chemicals structured by name comprising: a chemical name field; a chemical description field; a chemical type field; a chemical dosage units field; a chemical dosage measurement field; a chemical rate units field; a chemical rate measurement field; a chemical loading units field; a chemical loading measurement field; a chemical feed density units field; a chemical feed density measurement field; wherein the list of chemicals has been defined as part of said chemicals listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chemical input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ad) said sampling point logs listing module further comprises a form displayed on said computer screen wherein said sampling logs listing module form comprises: sampling point search fields comprising: a log date from search field; a log date to search field; a sampling point name selection search field; and a description search field; and a search button responsive to user input; a display element to display existing list of sampling point logs retrieved based on user entered search fields and structured by log date, log time, sampling point name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the sampling point log module; and an add new sampling point log button wherein said add new sampling point log button is responsive to user input and wherein the actuation of said add new sampling point log button causes the opening of the sampling point log module with empty fields; ae) said sampling point log module form further comprises: a plurality of sampling point log fields responsive to user input comprising: a log mode field; a log date field; a log time field; a log description field; and a sampling point name selection field; a log mode selection choice button that allows the user to select a master mode to collect sampling point log information for all processes and process stages for the plant in a single step; a log mode selection choice button that allows the user to select an individual mode to collect process sampling point log information for only one selected process and stage for the plant in a single step; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said sampling point log input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; af) said sampling point log parameters listing module further comprises a display element, said display element being capable of showing: a list of existing process parameters structured by name comprising; a parameter name field; a parameter description field; a parameter type field; a parameter units field; a parameter minimum value field; a parameter maximum value field; a parameter enforce minimum and maximum field; a parameter measurement field; a parameter special operands field; wherein the list of process parameters has been defined as part of said parameters listing module; and a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said parameter definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ag) said reports listing module comprises a display element, said display element capable of showing: a list of existing reports structured by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the report definition module; and an add new report button wherein said add new report button is responsive to user input and wherein the actuation of said add new report button causes the opening of the report definition module with empty fields; at least one run button wherein said run button is responsive to user input and wherein the actuation of said run button causes the opening of said report rendering module; and ah) said report definition module form further comprises: a plurality of report definition input fields responsive to user input comprising: a log date from field; a log date to field; a description field; a report type selection field; and a report sub type selection field; a save button displayed on said computer screen that is responsive to user input; and a data movement element capable of transferring the user-provided contents of said report definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ai) said report processes listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing processes generated using said process definition module; a check box for each process to accept or remove its usage in the report; aj) said report process streams listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing process streams generated using said process streams definition module; a check box for each process stream to accept or remove its usage in the report; ak) said report sampling points listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing sampling points generated using said sampling points definition module; a check box for each sampling point to accept or remove its usage in the report; al) said report parameters listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing parameters generated using said parameter definition module; a check box for each parameter to accept or remove its usage in the report; am) said report chemicals listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing chemicals generated using said chemical definition module; a check box for each chemical to accept or remove its usage in the report; an) said report rendering module form further comprises: a plurality of report rendering input fields responsive to user input comprising a report rendering type field; a submit button displayed on said computer screen responsive to user input; a data movement element capable of transferring the user-provided contents of said report rendering input fields to a computer memory in response to a signal from said submit button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; and a report rendering display element that displays the report data upon receiving an actuation signal from the submit button; ao) said charts listing module display element further comprises: a list of existing charts ordered by name and description; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the chart definition module; and an add new chart button wherein said add new chart button is responsive to user input and wherein the actuation of said add new chart button causes the opening of the chart definition module with empty fields; at least one run button wherein said run button is responsive to user input and wherein the actuation of said run button causes the opening of a chart rendering module; and ap) said chart definition module form further comprises: a plurality of chart definition input fields responsive to user input comprising: a log date from field; a log date to field; a description field; a chart type selection field; and a chart sub type selection field; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said chart definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; aq) said chart processes listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing processes generated using said process definition module; a check box for each process to accept or remove its usage in the chart; ar) said chart process streams listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing process streams generated using said process streams definition module; and a check box for each process stream to accept or remove its usage in the chart; as) said chart sampling points listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing sampling points generated using said sampling points definition module; a check box for each sampling point to accept or remove its usage in the chart; at) said chart parameters listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing parameters generated using said parameter definition module; a check box for each parameter to accept or remove its usage in the chart; au) said chart chemicals listing module further comprises a display element, said display element being capable of showing: an ordered list of names of existing chemicals generated using said chemical definition module; a check box for each chemical to accept or remove its usage in the chart; av) said chart rendering module form further comprises: a plurality of chart rendering input fields responsive to user input comprising a chart rendering type field; and a submit button displayed on said computer screen responsive to user input; a data movement element capable of transferring the user-provided contents of said chart rendering input fields to a computer memory in response to a signal from said submit button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; a chart rendering display element that displays the chart upon receiving an actuation signal from the submit button; aw) said users listing module comprises a display element, said display element is capable of showing: said list of existing users; at least one edit button wherein said edit button is responsive to user input and wherein the actuation of said edit button causes the actuation of the user definition module; and an add new user button wherein said add new user button is responsive to user input and wherein the actuation of said add new user button causes the opening of the definition module with empty fields; and ax) said user definition module form further comprises: a plurality of user definition input fields responsive to user input comprising: a user login name field; a user password field; a user contact field; a user address field; a user phone field; a user fax field; and a user email field; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the user-provided contents of said user definition input fields to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory; ay) said user functions listing module further comprises a display element, said display element being capable of showing: an ordered grid of users and modules with checkboxes to accept or allow a specific user to access a particular module; a save button displayed on said computer screen that is responsive to user input; a data movement element capable of transferring the updated contents of the display to a computer memory in response to a signal from said save button wherein said data movement element does not require user-supplied computer code to transfer said user input field content into said computer memory.
 13. A form based method for defining, recording, and reporting processing plant information, the method comprising the steps of: connecting a client computer to a server computer; entering processing plant definition information into forms displayed on said client computer wherein said plant definition information comprises: at least one parameter for a processing plant; at least one process for said processing plant wherein said process comprises at least one process definition and said process definition comprises at least one process parameter; at least one sampling point for said processing plant wherein said sampling point comprises at least one sampling point definition and said sampling point definition comprises at least one sampling point parameter; at least one sampling point log for said processing plant; and at least one report for said processing plant; saving said processing plant definition information to said server computer; entering a log datum for said plant into a form on said client computer; saving said log datum to said server computer; actuating a button on said client computer, the actuation of which sends a report to said client computer wherein said report comprises said log datum.
 14. Said form based method of claim 13 further comprising the step of entering user access rights information into a form displayed on said client computer.
 15. Said form based method of claim 14 wherein: entering processing plant definition information further comprises information for at least one process stream for said processing plant and said process stream information comprises a process stream definition, a list of process stream chemicals, and at least one process streams chemical definition; and said report comprises at least one process stream.
 16. Said form based method of claim 15 further comprising the steps of: defining charts; defining chart processes; defining chart sampling points defining chart parameters; defining chart chemicals; and rendering a chart to be displayed on said client computer.
 17. Said form based method of claim 13 wherein: entering processing plant definition information further comprises information for at least one chemical for said processing plant and said chemical information comprises a chemical definition; entering at least one process further comprises entering at least one chemical for said process; and said report comprises at least one chemical.
 18. Said form based method of claim 17 further comprising the step of entering organization information wherein said organization information comprises the step of identifying which processing plant belongs to which organization and the step of entering user access rights information further comprises the step of identifying which plants a user can access.
 19. Said form based method of claim 13 wherein said client computer and said server computer communicate using an internet protocol.
 20. A form based client-server system for defining, recording, and reporting processing plant information, the system comprising: a computer-readable memory wherein said memory is located in one from the group of a server computer, a client computer, and a combination of said client computer and said server computer; a computer program stored on the computer-readable memory and adapted to be executed on a processor wherein the computer program displays the following on a client computer: a plant definition input form for a processing plant; a list of processes for the processing plant; a list of sampling points for the processing plant; a list of sampling point logs for the processing plant; a list of reports for the processing plant; a list of parameters for the processing plant; a list of parameter definitions for the processing plant; a list of process definitions for the processing plant; a list of process parameters for the processing plant; a list of sampling points for the processing plant; a list of sampling parameters for the processing plant; a sampling point log parameters input form capable of receiving: a sampling point log parameter name; a sampling point log parameter description; and a sampling point log parameter measurement; a report containing data recorded on a plurality of sampling log parameters input forms. 